Work Modes & Steering
In web chat, choose a mode with the Change work mode button in the composer. Work modes guide how Elowen handles your next message. Steering adds guidance to a turn that is already running. You can also use work-mode commands in the CLI; platform channels do not have these controls.
Choose a work mode
The web chat composer has a Change work mode button. Choose Build, Plan or Workflow. The choice applies to messages sent from that chat surface.
In the CLI, use /build, /plan or /workflow. The interactive CLI starts in Build mode; use Shift+Tab or Ctrl+Tab to cycle through the modes. Configure the key in /keybinds. You cannot switch modes while viewing a delegated child; it keeps its mode from when it was started. For headless chat, pass a mode:
elowen chat --mode build
elowen chat --mode plan
elowen chat --mode workflow
What each mode does
Build lets Elowen work with tools and make changes, subject to the account's permissions.
Plan asks Elowen to work out an approach before editing. Ordinary mutating tools are blocked while planning. When the plan is ready, choose Implement plan to switch to Build and start implementation, or Cancel to keep planning. Plan mode is a permission guardrail, not a sandbox.
Workflow guides Elowen to organize work as a graph of sub-agents. It does not add permissions or automatically delegate every request. Learn more in Sub-agents & Workflows.
Steer a running turn
While a turn is running, send another message in web chat or the CLI to add guidance. Elowen queues it for the active run after its current tool round; it does not start a parallel turn in the same conversation. If the run finishes before the message is picked up, the message is used on the next turn.
In the CLI, when viewing a delegated child, plain text goes to the child. Slash commands still act on the parent conversation. Press Esc to return to the parent, Ctrl+O to switch between running children, or Ctrl+B to move foreground work to the background. Steering cannot give a child more access than it already has.
Shorten the conversation with /compact
Use /compact to summarize older conversation context and make room for new work. Add a note about what the summary should preserve:
/compact Keep the API decisions and the failing test details
Compaction removes older context from the active prompt. Your note guides the summary; it does not restore removed files or grant access.