Workspaces (worktrees)

Coming soon

Why each task lives in its own copy of the code, and how a workspace is created, used and deleted.

In the Taller, each task has its own workspace. Under the hood it's a git worktree: a copy of the repository on your disk, with its own branch. Instead of switching branches and stashing half-done changes in a single folder, each task has its own. That's why several agents can work at the same time without stepping on each other's files.

It's the same rule the platform follows: every task of the team of agents is visible and has its own workspace and branch.

How it works

Each project has a starting point (usually the main branch).
Each workspace starts from a branch or a commit you choose.
Each workspace has its own branch, its files and its terminals with agents.
Deleting a workspace removes the folder and the branch, always with confirmation.

A task's life cycle

Create: the task name, where to start from and, if you want, the link to the related issue or change.
Work: terminals with agents, editor and browser, all inside that workspace.
Review: the diff against the starting point, with line-by-line comments.
Deliver: commit, push and open the review, without leaving the Taller.
Archive or delete: one click removes the workspace and its branch.

Where to start from

When you create a workspace you can start from:

The project's main branch (the most common).
Another local branch, to stack work on top of a change that's still in review.
A specific commit.
A remote branch, which the Taller downloads for you.

Files git doesn't keep

A new workspace is a clean copy: it doesn't bring installed dependencies, caches or the local secret files that git ignores. So you don't have to redo them every time, you can:

Share heavy folders (like node_modules) between workspaces, by link.
Copy specific files (like .env.local) into each new workspace with a .worktreeinclude file at the root of the project:

# .worktreeinclude
.env.local
.vscode/settings.json

Branch name

By default, the Taller derives the branch name from the name you give the task. If you need an exact one (for example feat/payments), type it in the advanced options when creating the workspace.

Where it runs

A workspace can live on your computer or on another machine. See remote servers and SSH.