Quick start
Point commands at a repo that is already represented by a ForkTTY workspace or surface cwd; hidden repos are rejected by design.
forktty worktree-list --cwd /path/to/repoforktty worktree-create feature/my-task --cwd /path/to/repoforktty worktree-status --cwd /path/to/repoforktty worktree-attach feature/my-task --cwd /path/to/repoParallel work without checkout collisions
Each agent lane can get its own directory, branch, pane tree, and task state. A leader can keep mutating workers separated while read-only review workers share context when appropriate.
Visible repository boundary
Worktree socket, CLI, and MCP operations require an explicit repo path and validate it against repositories already represented by visible ForkTTY workspace or surface cwd. Hook-reported resume cwd is context, not authorization.
Safer cleanup
Worktree remove and merge flows check dirty state and linked worktree metadata before changing repository state. ForkTTY reports preconditions instead of silently operating on unopened repositories.
Questions
Why use git worktrees with AI agents?
Can ForkTTY create worktrees from the UI?
Can a socket client mutate any repo on disk?
Explore related ForkTTY pages
Get the alpha build
AppImage and .deb packages are published on GitHub Releases for Linux x86_64.
View releases