Local context
On your device, with a clear path out.
Projects and conversation history are stored locally. Relevant prompts, files and tool results may still be sent to your chosen model or connected service.
Privacy & control
Your workspace. Clear boundaries.
Know where your work lives and what you allow. Local storage, online models and connected tools each have a different role.
Plan · Work · Codemode
Space to think before you act.
Investigate and review without changing files. Plan cannot run Shell, MCP or executable extensions; you choose when to proceed. Edit files and run tools under the selected approval policy. Work is the default for new tasks. Coordinate tools through scripts for multi-step work. Codemode follows the same permissions and approvals as Work.
Credentials
Protected by your operating system.
API keys and connection credentials use operating-system encryption. Secret storage fails if protection is unavailable. This does not encrypt all project files or conversations.
Tools & extensions
Permission belongs to each tool.
Local MCP servers use native isolation by default, with individual network and compatibility settings. Executable extensions require explicit trust. Full local access applies only to extensions. Approved Shell commands and the integrated Terminal use desktop-user permissions. Local MCP is isolated by default; a justified, approved single-call escalation does not change saved permissions.
IM permissions
Share work within the scope you choose.
Authorize projects, folders or files for each audience. Write, command and network permissions are separate. Group membership alone never grants access to your computer.
Connect with understanding.
Read how accounts, model processing, retention and deletion work before bringing sensitive information into a task.
Read the privacy policy