Coming from agent teams

Agent teams, their engine and their board became projects, issues and the runner. Your teams move over when you choose to.

What changed

Teams
A team becomes the project of its folder, and the folder its repository. See Projects and repositories.
The board
A team's cards are now a project's issues, on the Board and the List of its Issues view.
The engine
The runner replaced it. A run is one issue worked by Claude Code in a worktree of its own, started from the issue and reviewed there. See The Runner.
Claude in a terminal
Still yours to run: the Claude profile and Claude in a folder open it, and the pane is called Claude while it runs.
Issues from files
Files agents wrote into a repository's .splitterm/issues folder are no longer read. Paste several issues into the composer instead: see Several at once.

Move to projects

  1. When an earlier version left teams on this machine, the sidebar offers Move to projects once. Not now puts the offer away; the command palette keeps Move teams to projects.
  2. Pick the teams to move. Each team's folder becomes a project, or joins the project that already has it, and its cards become issues in board order, with their title, text and priority. Done cards arrive done.
  3. Choose whether persona names stay on the issues as a label. Runs do not use them.
  4. On Free, choose the project that keeps issues and the runner.

Nothing converts on its own, and moving a team twice does nothing. The old board could not tell your cards from the ones agents filed, so a run of a moved issue starts in careful mode until you trust its text.

Old team files

After the move, a project's Settings offers to clean up what the old engine left in each repository: its context and status files, its two hooks in .claude/settings.local.json and its lines in git's exclude file. Every change is shown as a diff first, your own hooks and settings stay, and only what is still as shown is changed. Files agents left in .splitterm/issues are listed by name, never opened, and go only if you tick them.

Older branches

The old engine's worker folders are listed under Older branches, in the footer of Runs and in the command palette, with their git state and the issue they were on. A folder can go only when its work exists somewhere else, and its branch always stays.