Workspaces
Where agents work on code and files, how a task's workspace is chosen, and how to inspect its files, branches, services and logs.
A workspace is the folder an agent works in: a checkout of your repository, a branch, or a sandbox. Tasks that change code or files run in a workspace, and you can open it to see exactly what the agent changed.
How a task gets a workspace
The project's workspace policy decides:
| Policy | Effect |
|---|---|
| Shared workspace | Tasks in the project share one checkout. Good for small teams of agents taking turns. |
| Isolated workspace | Each task gets its own worktree on its own branch, so agents never step on each other. |
| Reuse existing | The task continues in a workspace you choose. |
| Agent default | The agent's runtime decides, for example a cloud sandbox. |
Set the policy in the project's Configuration. A single task or routine run can override it.
Inspect a workspace
From a task, open the workspace card or the Files panel. From the left menu, Workspaces lists every workspace with its project, branch and state. A workspace page shows:
- Files and the repository state (branch, changes).
- Services the agent started, such as a development server, with their logs and addresses.
- Runtime logs of setup and teardown commands.
- Configuration: the commands that prepare and clean up the workspace.
Services
Agents can start long-running services in a workspace, for example a web server to test a change. Start and stop them from the Services tab. A running badge means the process is up; open its address to check that it actually answers.
Closing and cleanup
When a task finishes, its workspace is kept for a while so you can review the result, then compacted. Before anything is removed, Veyra saves a restore point of the work, so finished work is not lost when the files on disk are cleaned up.
Related
- Projects and goals
- Workspaces and Environments in the API reference.