PERMISSIONS AND ACCESS
ARTEI only reaches what you choose.
Conversation does not automatically unlock files, cameras, media, devices, software tools or specialist agents. Each capability has a separate grant you can review, pause or remove.
Owner Chat
Talk with ARTEI and act on inline approvals, running status, media previews, forms, and build progress.
Desktop Companion
Tray presence, global hotkey, notifications, owner-to-ARTEI command, and file handoff.
Mobile & PWA
Phone-first approvals, notifications, camera and microphone path, and account-synced sessions.
Files
Scoped file handoff, uploads, downloads, previews, and future native folder grants.
Camera & Mic
Explicit per-use grants for capture, voice input, and future native companion workflows.
Voice
Voice input, ARTEI speech, audio passthrough planning, and real-time session readiness.
Avatar Video
A path to talking video presence for ARTEI using realtime avatar or hologram-style embodiment.
Media Creation
Create and share images, video, audio, documents, and previews through governed tools.
Build & Run
Prompt, edit, preview, deploy, and hand off software from an owner-approved build surface.
Plugins & Specialists
Approved skills, connectors, and specialist agents are callable through one audited registry.
Deploy & Share
Ship outputs, send share links, and direct invites to the public site instead of private workspaces.
Notifications
Desktop and mobile alerts for approvals, stalled work, defensive posture, and completed tasks.
ACCESS MODEL
Access is a grant, not an assumption.
Default off
Every sensitive capability starts unavailable until the owner grants a specific scope.
Scoped grant
ARTEI receives a narrow capability, such as a folder, microphone session, or build tool.
Audit and revoke
Every privileged action is logged, and the owner can revoke a capability mid-flight.
Build access stays contained
ARTEI can be allowed to read, edit, run, preview and deploy software. Approval comes first, isolated testing second and a deliberate release last.
Share without exposing the workspace
Public links should invite people to ARTEI or WUBBERY, not open a private companion workspace. True multi-user workspace access is a separate owner-approved capability.
Useful access should always have a clear way back.
Start with conversation. Add files, media, devices, build tools or specialists one capability at a time.