Code mode
Code task type targets software engineering: read the repo, run commands, review diffs, and iterate with LHT / CRAFT-style harness tools.
Workspace
Point Zagens at a git checkout or project folder. The agent can:
- Search and edit source files (
grep_files, symbol index) - Run commands in a workspace terminal under the Windows native sandbox
- Produce patches you review in the diff preview
See Workspace overview for the file tree and snapshots.
UI areas (Code)
| Area | Use |
|---|---|
| Workspace panel | Tree, preview, diff, terminal |
| Browser | Built-in Browser and local preview |
| Night queue / Agent health | Batch gated jobs and tool telemetry |
| Checklist sidebar | Long-horizon task steps |
| Audit grid / float cards | Checklist, scratchpad, LHT, sub-agents |
| Replay | Past tool calls and timeline |
Full layout: UI tour.
When to use Code vs Office
| Task | Mode |
|---|---|
| Refactor, tests, CI fixes | Code |
| Competitive brief, quote spreadsheet, executive daily | Office |
Tips
- Keep one workspace per repository for clearer context.
- Use explicit goals ("add unit tests for
foo.rs") for faster iterations. - Large monorepos: mention the crate or subfolder you care about in the first message.
- Risky shell commands may show an approval dialog — configure under Settings.
Deep dives: LHT · Gate-as-Code · CRAFT · Night queue · Audit scratchpad