Session Branching

🌐 Language: English | 中文

Session Branching & Cross-Engine Pipeline

KinetAios supports session branching — creating a new conversation that inherits the context of an existing one, optionally switching engines. This enables cross-engine pipelines where different engines handle different stages of a task.

How it works

• Branch: create a new session from an existing one's context. The new session inherits the conversation history.
• Cross-engine: branch from a Direct session to Claude Code (or vice versa). The new session uses the target engine with the prior context.
• Agent task graph: visualize the branch tree — which session spawned which.
• Context handoff: when branching, the directHistory (raw tool-call history) is passed to the new session so the AI has full context.
• Memory sync: long-term memory is shared across all sessions (see Long-Term-Memory).

Use cases

1. Start with Direct, finish with Claude Code: Direct does the exploration/planning, then branch to Claude Code for execution.
2. A/B testing: branch the same context to two different engines and compare (see Arena).
3. Context compression: branch a long session to a fresh one with compressed context.
4. Task handoff: export a session, import on another machine (see MCP-Server).

Visualization

• Agent task graph: shows the branch tree — parent sessions and their children.
• Context compression view: visualizes how context was compressed during branching.

Source files

File	Purpose
src/main/TaskManager.ts	Session branching, context handoff, directHistory passing
src/renderer/app.ts	UI for branch command

Related

• Engines — the three engines
• Arena — side-by-side comparison
• MCP-Server — remote session export/import