Quick start
Compare ForkTTY by testing the concrete surfaces it adds around a normal terminal: capability discovery, compact context, worktrees, and team review.
forktty capabilitiesforktty context-snapshot --tail-lines 0 --jsonforktty worktree-list --cwd /path/to/repoforktty team review review-team reviewer --task-id review-head --commit HEAD --submitCompared with terminal multiplexers
tmux, screen, and similar tools are excellent for persistent terminal layout and remote shells. ForkTTY focuses on local GTK workspaces, agent lifecycle metadata, prompt-aware notifications, git worktree flows, and MCP/socket automation.
Compared with agent dashboards
Agent dashboards often abstract away the terminal. ForkTTY keeps the real terminal visible and treats orchestration state as a layer around it, so approvals, tests, and unexpected output stay inspectable.
Compared with hosted coding agents
Hosted agents can be convenient, but they move execution into a service. ForkTTY is local-first: bring your own CLI, account, repository, and Linux desktop; ForkTTY coordinates what runs there.
Questions
Should I use ForkTTY instead of tmux?
Is ForkTTY an AI agent by itself?
Is ForkTTY production-stable?
Explore related ForkTTY pages
Get the alpha build
AppImage and .deb packages are published on GitHub Releases for Linux x86_64.
View releases