From project to reviewed work

Spaces and worktrees

A space associates a name with a project path. Its house accommodates sessions from that project, with one floor per buddy and room for active sub-agents. Agents waiting for a response join the shared desk.

Managed sessions launched in Git can work in separate worktrees. This isolates their files but does not replace a review or a merge strategy. Buddies does not merge your changes for you.

Changes

The Changes tool applies to the selected session. It displays Git changes and lets you annotate added or context lines. If the diff has changed since annotation, sending the review is blocked to avoid commenting on the wrong revision.

A non-Git folder, a read error or a volume limit must be distinguished from an empty diff. Refreshing does not fix structural causes such as too many untracked files.

Missions

Describe the work or import a GitHub/Linear issue. Choose the project and provider, then define successive roles if needed: development, testing, review.

A mission team works sequentially. The next worker inherits the worktree and approved context; it does not start just because the previous worker is idle. You approve the result between stages.

Progress and checks

Progress checkpoints are explicit updates. From a session with the CLI available in its PATH:

buddies progress ID 'Tests complete, review pending'

Checks run in the buddy’s folder and retain their results and logs. Use commands that finish, not a server or an ongoing watch mode. If a worker disappears, its result becomes unknown rather than being assumed successful.

Preview

Start your project’s server, then open its address in Preview. Once the page has loaded, select an element to give your agent context. Page content remains external input, not permission to execute its instructions.

Compare

Choose two compatible approaches and review their context, branch and changes. Comparing does not merge branches or automatically decide which solution is best.