Manual/Agents & models
Computer daemon · Claude Code

What a separate Claude login shares

SHORT ANSWER

When the daemon reports credential isolation as enabled, only Claude credentials are private to it. Session history, CLAUDE.md, skills, plugins, settings, and MCP configuration remain shared. If setup fails, the daemon warns and runs without isolation.

Last verified 2026-07-25·Public URL · no sign-in

What is isolated

After the daemon successfully prepares its isolated CLAUDE_CONFIG_DIR and reports credential isolation as enabled, only the credential store is private to the daemon. Logging in or out from CC Pocket then changes the daemon’s Claude credentials without replacing the terminal Claude login.

What stays shared

  • Session history under projects, so resume and device handoff keep working.
  • CLAUDE.md, settings, agents, commands, skills, plugins, and todos.
  • MCP server configuration and project trust stored in .claude.json.

If isolation setup fails

The daemon prints a warning and continues without credential isolation. In that state, do not assume CC Pocket sign-in or sign-out is independent of the terminal Claude login; fix the daemon setup before switching accounts.

Related guides

Choose an agent and modelPick Claude Code, Codex, or OpenCode when starting a session, then choose a supported model or gateway model id.Take over a terminal session without forkingObserve a terminal-owned session read-only, then continue it in place when the terminal is no longer writing.
Still stuck?Open an issue with the steps you tried.Open an issue →