OpenCode runtime
OpenCode is the most sidecar-oriented runtime in Jarvis today. It is useful when you want a session model that exposes structured permissions and terminal attachment through the OpenCode local session APIs.
Good fit
Section titled “Good fit”Use OpenCode with Jarvis when you want:
- a managed runtime with a sidecar-backed session model
- terminal attachment through OpenCode’s own session and PTY surfaces
- structured permission requests that Jarvis can surface and reply to
- worker MCP reporting for managed sessions
Prerequisites
Section titled “Prerequisites”- OpenCode installed and available as
opencode, or configured through Jarvis runtime settings - a working local OpenCode auth and provider setup
- the ability to run the local OpenCode sidecar required by your installation
What Jarvis manages
Section titled “What Jarvis manages”For managed OpenCode sessions, Jarvis can:
- launch or resume an OpenCode session in a workspace
- attach terminal output to Jarvis
- inject Jarvis worker MCP reporting tools
- watch OpenCode permission requests and surface them as intervention work
- include OpenCode activity in Session OS and summary capsules
OpenCode support is more dependent on the local sidecar health than the other runtimes. When the sidecar is unavailable, Jarvis can usually explain that failure, but the runtime will not behave like a plain terminal-only fallback.
What stays in your OpenCode setup
Section titled “What stays in your OpenCode setup”These remain in your local OpenCode environment:
- your account and provider credentials
- your global OpenCode defaults
- any non-Jarvis sessions you run directly with the CLI
Jarvis integrates with the local OpenCode session layer instead of becoming a replacement credential store.
Common failures
Section titled “Common failures”opencode is not found
Section titled “opencode is not found”Jarvis cannot launch OpenCode until the CLI is installed or the command path is configured correctly.
The sidecar is unreachable
Section titled “The sidecar is unreachable”This is the most common OpenCode-specific failure. Jarvis may show terminal attachment or control features as degraded when it cannot reach the local OpenCode sidecar.
Permission actions do not resolve
Section titled “Permission actions do not resolve”OpenCode permission replies are routed through the local sidecar and depend on the session directory context. If the sidecar lost that context, a pending permission may remain unresolved until the session is refreshed.
Local discovery behavior differs from managed launch behavior
Section titled “Local discovery behavior differs from managed launch behavior”OpenCode discovery is tied to local session and sidecar state. A session started outside Jarvis may still be visible, but exact attach and intervention behavior depends on that local runtime state.