Claude Code runtime
Claude Code is the most direct fit if your day-to-day agent workflow already lives in Anthropic’s official CLI and terminal UI.
Good fit
Section titled “Good fit”Use Claude Code with Jarvis when you want:
- a familiar interactive Claude CLI session, supervised from Jarvis
- strong session discovery and transcript-backed replay
- worker MCP reporting without teaching the CLI a separate Jarvis workflow
- optional human approval gates for sensitive tool use
Prerequisites
Section titled “Prerequisites”- Claude Code installed and available on your machine as
claude, or configured through Jarvis runtime settings - a working Claude CLI login and whatever local auth your Claude Code setup normally expects
- a workspace directory Jarvis can launch in
What Jarvis manages
Section titled “What Jarvis manages”For managed Claude Code sessions, Jarvis can:
- launch and label the session from the control tower
- stream terminal activity into Jarvis
- inject worker MCP reporting tools for managed workers
- discover compatible local sessions and keep them visible in Session OS
- build summary capsules so the main chat can track active work without full terminal replay
- surface blockers and human questions through Jarvis intervention flows
Jarvis uses launch-time flags and temporary Jarvis-owned config files for this integration. It does not require you to re-authenticate inside Jarvis.
What stays in your Claude CLI setup
Section titled “What stays in your Claude CLI setup”These remain outside Jarvis:
- your Claude account login
- your normal Claude CLI defaults and personal habits
- any global Claude configuration that is not needed for a Jarvis-managed session
Jarvis can pass session-specific MCP or prompt wiring when it launches a worker, but that is scoped to the launched process rather than a permanent takeover of your global CLI identity.
Common failures
Section titled “Common failures”claude is not found
Section titled “claude is not found”Jarvis cannot launch the runtime until the Claude CLI is installed or the command path is configured correctly.
The session launches, but worker reporting never appears
Section titled “The session launches, but worker reporting never appears”That usually means the managed worker did not receive the MCP launch wiring or the local Jarvis MCP endpoint was unreachable. Re-launching the session from Jarvis is the fastest check.
Approval cards do not appear
Section titled “Approval cards do not appear”Claude Code approvals in Jarvis depend on the local gating mode. By default, Claude Code is more permissive than OpenCode’s structured permission flow. If your setup is not using gated approvals, intervention may remain observe-only.
Resume behavior looks different from a fresh launch
Section titled “Resume behavior looks different from a fresh launch”Claude Code resume inherits the runtime’s own session semantics. A resumed session may surface different prompts or condensed context depending on the size and state of the original CLI session.