A workspace keeps the context of a task together. Organize work inside a project and access agent conversations, directory files, terminals, and Git changes.
Projects and workspaces
A project corresponds to the code directory you work in. A workspace organizes particular work and sessions. Agents execute in the selected working directory; creating a session does not automatically create a separate copy of the code.
Add a project first, then create its workspace. When using an existing directory, confirm that it contains the correct code, configuration, and project instructions.
Give the agent context
When creating an agent, describe the intended result, relevant files, and verification method. For example:
Add responsive navigation to this project. Follow the existing styles, check the mobile layout, and run the project’s current build command.
Agents use their native configuration. See Agent setup for how project instructions, skills, and tools are loaded.
Inspect and verify changes
- Follow the agent’s work in the conversation.
- Open files and diffs to inspect the changes and scope.
- Run the project’s build or verification commands in the terminal.
- Add feedback or proceed with your next Git action.
The homepage demo illustrates this workflow. It does not run real tasks or modify your files.
Git worktrees
Use the project’s Git worktree workflow when you need separate directories for parallel tasks. A worktree gives the same Git repository multiple working directories, each with its own branch and file state.
Check the repository state and target branch before starting, then review changes before merging. Worktrees separate directories and branches; they are not an operating-system security sandbox. Project setup may still be running after workspace creation. Wait for dependency installation and initialization before starting work.
Commits and pull requests
The primary workspace action follows the actual Git and PR state, offering actions such as commit, create PR, push, or view PR. GitHub/GitLab operations also require Git and the appropriate gh / glab authentication on the working host.
“View PR” opens the existing request; it does not push commits. Resolve conflicts, divergence, or a behind branch before continuing. After merging, check for active agents and unanswered approvals before archiving the workspace.
Scheduled tasks
Open schedules from the workspace’s new-item menu. Choose an existing agent or a new agent for each run, then configure the prompt, interval or Cron expression, timezone, and run count. A task belongs to that workspace. Create a worktree workspace first if it needs an isolated directory.
Tasks run on the working host’s daemon. Closing a client tab does not stop an online daemon’s scheduler. Tasks do not execute while the host or daemon is offline, and recurring schedules do not replay every missed occurrence. Pausing prevents future automatic triggers; cancel an active run separately.
Pick up on another device
After connecting to a working host, remote devices access its workspaces. Files and runtimes stay on the host. A remote connection does not copy the project to your phone.
See Connections & data for connection methods and platform differences.