Build on your machines
Optimal does its work on a machine: a sandbox or a computer. You choose which one before it starts.
Choosing a machine
In Build mode, a “Where should you build?” sheet rises from the composer. You can either:
- create a new sandbox, which is small, has an idle timeout of 1800 seconds, and has the purpose
optimal_build; or - pick a machine you already have.
Cancel keeps your draft.
A harness brain always asks where to work, in any mode, because it is a run on a machine.
The side workspace panel
When work starts, the workspace panel opens on the right and follows the bound machine. Its tabs:
| Tab | Shows |
|---|---|
| Progress | The steps the agent is taking |
| Preview | A live URL when the agent serves one |
| Files | The files the agent wrote |
| Code | Diffs from file writes |
| Terminal | A shell on the machine |
| Machine | The bound machine |
| Artifacts | Files the run produced |
| Deployments | Apps published from the machine |
| Logs | The run’s raw output |
The Machine tab shows the machine the chat is bound to.
Stop, take over, hand back
- Stop cancels the running brain.
- Take over interrupts the brain and shows “You’re in control”.
- Hand back sends one message that continues the same chat.
Sending a message also hands back. Nothing is interrupted if nothing was running.
Related
- Optimal: brains, modes, and the cost strip.
- Chat with an agent on a machine: the same chat from a computer or sandbox page.