Use Lookout
Modes
Agent and Ask tell the agent what a chat is for, Multitask splits Agent's work across subagents, and you can switch at any time.
Every chat has a mode, and the mode tells the agent what the chat is for. A chat in Ask shows its mode as a chip in the message box; Agent shows none.
| Mode | What it's for |
|---|---|
| Agent | Edit files and run commands |
| Ask | Answer questions without changing files |
A mode is an instruction the agent follows, not a lock: in every mode it has the same tools and the same access to your machine. See Safety. Multitask is an option of Agent mode: it splits the work across parallel subagents.
Switch modes
The chat keeps its history when you switch. A switch made while the agent works applies from its next turn. The agent never switches its own chat's mode.
On Home, the Ask pill under the message box switches to Ask, and Tour this workspace sends a request for a tour of the project right away (in a project's first chat, not in Scratch). Click a pressed pill again to go back to Agent. Settings › Chat › Show on Home chooses whether Home offers Multitask and Ask; Ask is off by default.
Ask without changes
In Ask, the agent reads and searches your code and runs commands to answer you, without changing files. Switch to Agent when you want the changes made.
Split work with Multitask
In Agent mode, Multitask in the + menu turns it on, as does picking Multitask with ⇧Tab. While it is on, a Multitask chip in the message box says so; its × turns it off. The agent then hands substantial work to subagents it doesn't wait for, so the chat stays free while they work. Multitask stays on until you turn it off. How the subagents work is on Subagents.
The chip shows while Settings › Chat › Composer › Multitask in the composer is on, as it is by default. Turning it off hides the chip and leaves each chat's mode as it was. On Home, where the Multitask pill under the message box already reads pressed, the chip stays out.
Modes in the CLI
lookout exec, lookout resume and lookout set take --mode, with agent, ask or multitask:
lookout exec "Explain how the login flow works" --mode askThe base mode and orchestration level are independent. --mode agent and --mode ask select only the base mode; they do not turn Multitask off. A new chat without its own orchestration setting inherits its project's last-used level, including in a reused Scratch project. resume and set leave settings you omit as they are, including inheritance.
Use --no-multitask to pin orchestration off before the prompt runs. Alone, it leaves the base mode unchanged; with --mode agent, it selects Agent with orchestration off. It can also accompany --mode ask.
lookout exec "Make the change" --mode agent --no-multitask
lookout resume CHAT "Continue the change" --no-multitask
lookout set CHAT --no-multitask --on localThe flag also works with exec --on MACHINE, set --on MACHINE and the LOOKOUT_MACHINE default. --mode multitask remains the shorthand for Agent with Multitask on; combining an explicit on selection with --no-multitask is a usage error and starts no work. Turning orchestration off does not remove tools, permissions or machine access: it is not a security boundary.