Docs

Focus Mode

Focus Mode gives the orchestrator room to work while keeping the chat stable. The sidebar slides over the workspace, the chat stays centered, and a compact right rail shows high-level progress instead of raw tool telemetry.

Live work rail

For non-trivial work, the orchestrator can publish a human checklist to the right rail withlive_plan_update. The rail is intended to answer: what is planned, what is active, and what is already done.

StateMeaning
pendingA planned step that has not started yet.
activeThe step the orchestrator is currently working on.
doneA completed step. Done items remain visible long enough to understand progress.
errorA step that failed or needs attention.
Note:The rail should show human work items such as "Inspect context", "Implement docs", or "Run validation". It should not show low-level tool names such as grep, read files, or shell commands.

Goal progress

When a current goal is linked to issues, Focus Mode can show the goal and its issue rows in the same rail. Done issues are checked off, active issues are highlighted, and open issues remain visible without opening the full drawer.

Environment section

The same card can include a compact Environment section backed by existing Agenties data: project name, phase, branch, and dirty-file count. Unsupported rows are omitted instead of using placeholders.

Layout rules

RuleReason
Chat stays centeredOpening or hiding the sidebar should not push the active conversation around.
Workspace sections may shiftNon-chat sections move to avoid being covered by the expanded sidebar.
One unified cardProgress, goal rows, and environment context live in one rail card instead of stacking unrelated cards.
No activity dumpActivity and files stay in their drawers unless explicitly opened.