Glossary
API key
Section titled “API key”A local authentication credential used to access a Jarvis instance. Jarvis stores only a hash of the key, not the original secret.
cc-brain
Section titled “cc-brain”An optional mode where Claude Code acts as the main orchestration brain for other coding sessions.
Coding session
Section titled “Coding session”A Jarvis-managed or discovered runtime session for tools such as Claude Code, Codex, or OpenCode.
Main chat
Section titled “Main chat”The primary Jarvis conversation surface where the human sees assistant replies and worker reports together.
Managed session
Section titled “Managed session”A coding session launched and tracked directly by Jarvis, rather than only discovered after the fact.
Model Context Protocol. In Jarvis, it is used as the structured tool channel between worker runtimes and the Jarvis backend.
Minimal core
Section titled “Minimal core”Jarvis’s current product focus: reliable chat plus coding agent orchestration, with non-core experimental systems kept disabled or out of the default path.
OpenCode
Section titled “OpenCode”One of the supported coding runtimes that Jarvis can launch, discover, and monitor.
Orchestrator
Section titled “Orchestrator”The Jarvis backend and UI acting together as the control layer for chat, sessions, and worker reporting.
Persistence
Section titled “Persistence”The design principle that messages and stream events are written to storage so they can survive refreshes, reconnects, or transient client loss.
Remote control
Section titled “Remote control”An optional channel, such as Telegram, that lets the operator interact with Jarvis when away from the local machine.
Runtime adapter
Section titled “Runtime adapter”The Jarvis integration layer for a specific coding runtime, such as Claude Code, Codex, or OpenCode.
Runtime session
Section titled “Runtime session”A session owned by an underlying runtime process. Jarvis may launch it, discover it, observe it, or take over management of it.
Session OS
Section titled “Session OS”Jarvis’s session-management layer for discovering, replaying, viewing, and taking over coding runtime sessions.
Server-Sent Events. Jarvis uses SSE to stream chat output and certain live updates over HTTP.
Stream event
Section titled “Stream event”A persisted event frame in a Jarvis turn, such as a token delta, tool call, error, or terminal completion signal.
Summary capsule
Section titled “Summary capsule”A low-noise snapshot of active session state pulled into the main conversation so the orchestrator can stay aware without ingesting raw terminal output.
Worker
Section titled “Worker”A coding runtime session acting on a delegated task under Jarvis orchestration.
Worker MCP reporting tools
Section titled “Worker MCP reporting tools”The small set of MCP tools a worker uses to report progress, surface blockers, ask for human input, or request more context.
Knowledge base
Section titled “Knowledge base”An optional personal memory store that can be queried through search_kb. It is not required for Jarvis to run.