Workspace overview
A workspace is the folder Zagens agents read, edit, and run commands in. Prefer one directory per project or office inbox.
Choosing a workspace
- On first launch or via sidebar Workspace.
- Point at a git repo (Code) or an office folder with
inbox//data/(Office). - Sessions bind to the workspace path — switching folders switches the session list.
Composer ⋯ → Session isolation (git worktree) can create an isolated tree under .worktrees/ for parallel sessions.
Code vs Office layout
| Mode | Typical layout |
|---|---|
| Code | Repo root; terminal, diff, symbol index, Browser |
| Office | inbox/ briefs, data/ sheets; outputs in deliverables/ |
See Office workspace.
What you can do
- Browse the file tree — File tree
- Preview supported formats (including visual HTML) — File preview
- In Code: embedded terminal, Diff, snapshots
- Open Built-in Browser for localhost / external verification
- Use sidebar Night queue for batch jobs
Tips
- Prefer a dedicated folder — not disk root or your home directory.
- For large monorepos, name the crate/subdir in the first message.
Related: File preview · Terminal · Built-in Browser