Launch a session
Start a managed coding session from Jarvis so the work appears in the session list and can report status back to the main chat.
Prerequisites
Section titled “Prerequisites”- Jarvis is running and reachable from your browser or desktop app.
- At least one supported runtime is installed and authenticated on the same machine as Jarvis.
- You know which task you want the worker to handle first.
-
Open the coding session launcher Go to the session area in Jarvis and choose to create or launch a new coding session.
-
Select a runtime Pick Claude Code, Codex, or OpenCode based on what is installed and ready on the machine.
-
Write the launch instruction Describe the task clearly enough that the worker can begin without immediate back-and-forth. Include the target repo or working context if the UI asks for it.
-
Start the session Confirm the launch and wait for the new managed session to appear in the session list.
-
Watch for early signals Use the summary capsule to confirm the worker has started. If the runtime supports reporting, early MCP signals may also appear in the main chat.
-
Leave the session running or open it directly Stay at the control-plane level for supervision, or open the full session if you need to inspect detailed behavior right away.
Verify
Section titled “Verify”The launch worked when:
- a new session appears in Jarvis shortly after you submit the task
- the session is marked as managed rather than discovered from an external runtime
- the runtime and status are visible
- the main chat shows capsule-level awareness of the session, with MCP updates if the worker emits them
Troubleshooting
Section titled “Troubleshooting”The runtime does not appear as an option
Section titled “The runtime does not appear as an option”The runtime may not be installed, authenticated, or available to Jarvis on the current machine. Confirm the CLI is set up before retrying.
The session launches but immediately stalls
Section titled “The session launches but immediately stalls”Open the session and inspect the early transcript. Common causes are missing auth, missing repository context, or a task prompt that is too vague to execute safely.
I started work manually in a terminal and now want Jarvis to see it
Section titled “I started work manually in a terminal and now want Jarvis to see it”Do not relaunch the same task unless you want a new managed session. Instead, inspect the discovered local runtime session from the session list.