Claude Code
Run Mopheus agent tasks with Anthropic's Claude Code CLI.
Claude Code
Mopheus runs Anthropic's claude CLI as a native provider. Install it on the machine that runs the Mopheus daemon; the daemon discovers it and registers a Claude runtime automatically.
Runtime
| Field | Value |
|---|---|
| Binary | claude |
| Path override | MOPHEUS_CLAUDE_PATH |
| Verify | claude --version |
| Protocol | Native |
| Interaction delivery | Active-turn steer, with next-turn fallback |
| Mopheus-managed MCP | Supported |
| Task skill path | .claude/skills/ |
| Filesystem sandbox | Supported on Linux |
Install Claude Code using the official installation guide, then start the daemon. An agent whose provider value is claude is dispatched to this runtime.
For a binary outside $PATH:
export MOPHEUS_CLAUDE_PATH=/opt/anthropic/bin/claude
mopheus daemon startUnattended tasks
Mopheus runs Claude Code non-interactively and requests bypassPermissions. Run the daemon as a regular system user when possible. Claude Code normally refuses this mode under root or sudo; host settings or managed policy can also disable it with permissions.disableBypassPermissionsMode.
When bypass mode is unavailable, pre-allow exactly the tools needed by unattended tasks in the daemon user's ~/.claude/settings.json. A tool requiring confirmation cannot wait for interactive approval and may be rejected. See the Claude Code permission modes and permission configuration.
Sessions and sandbox
Mopheus keeps Claude resumable session history workspace-scoped, including when the filesystem sandbox is disabled. Credentials, global CLI preferences, plugins, and other host-global data remain owned by the daemon user and are not copied into a workspace. Existing host-global session history is not migrated automatically.
On Linux, the optional filesystem sandbox uses an outer bwrap mount namespace. It exposes only the current task working directory and the task's managed data at the locations Claude Code expects.