Continuous session (Jarvis mode)
The continuous session is one long conversation per workspace. The main conversation is the voice you talk to; it dispatches background workers for anything that needs hands, and keeps the thread across tasks. The desktop sidebar calls it 你的贾维斯 (Your Jarvis).
Open it
In the desktop client, click the 小荷 pin at the top of the sidebar. If the workspace already has a continuous session, the pin opens that one — there is exactly one per workspace. It requires the Claude backend; other backends show “Xiaohe currently supports Claude only”.
How it works
The main conversation can only:
- launch a background worker (
Agent); - continue a worker it already launched (
SendMessage); - put a decision to you (
AskUserQuestion); - write durable memory;
- read the session history.
It cannot run commands, read files, edit files, or browse the web itself. Those actions belong to workers. This split is deliberate: the main thread stays responsive and keeps the plan, while workers do the work in the background.
What you see
| Surface | What it shows |
|---|---|
| Conversation | Normal prose replies; the main thread reports outcomes, not step lists |
| “正在办” (in progress) | Background workers and their status |
| “记忆” (memory) | Durable notes the assistant has kept; you can delete individual notes or clear all |
| Notifications | Worker completions; they are stored and can be replayed after a reconnect |
Memory and history
- Durable notes live with the session and survive context trimming.
- The main context is bounded. Older turns are archived, not lost.
- Ask “what did we decide about …” and the assistant can query the archive. From a terminal:
xiaohe history path
xiaohe history digest
xiaohe history query --grep 'keyword'
Using it well
- State the goal and the constraints once; the main thread carries them into the worker brief.
- For a follow-up on work already in flight, ask to continue it rather than starting over. The worker keeps its context.
- Decisions are yours: the assistant should present concrete options with a recommendation, not silently guess.
- Long tasks are expected. You can close the app; completions are persisted and delivered when you return.
Troubleshooting
| Symptom | What to do |
|---|---|
| The sidebar is stuck on a deleted session and logs show repeated 404s | Click the 小荷 pin or switch to another session; restart the client if it persists |
| Messages repeat, arrive out of order, or disagree with the transcript | Session menu → smart sync; use force rebuild only if smart sync does not settle it |
| A worker stays “in progress” | Check the in-progress panel; ask the main thread to continue it or explain the blocker |
| The assistant forgot an earlier decision | Ask it to search history; or write the decision to memory |
| You want a plain one-question chat | Start a normal session; the continuous one stays untouched |
Difference from a normal session
| Normal session | Continuous session | |
|---|---|---|
| Lifetime | One conversation, create as many as you like | One per workspace, long-lived |
| Tools | The main thread uses tools directly | The main thread dispatches; workers use tools |
| Memory | Mostly the conversation context | Durable memory, archive, replayable notifications |
| Best for | One-off questions and short tasks | Ongoing work, parallel tasks, a long-running assistant |