Quick start
Register the local stdio bridge, confirm the running socket capabilities, then take a compact snapshot before using mutating tools.
forktty mcp setup --dry-runforktty capabilities --jsonforktty context-snapshot --tail-lines 0 --jsonOne automation surface
The CLI, MCP bridge, and GTK app share the same socket behavior. That keeps workspaces, surfaces, status, notifications, worktrees, workflows, and teams consistent across human and agent interactions.
Compact context first
Agents can start with cheap reads such as identify and context snapshots before taking action. Snapshot defaults are compact: team details, workflow details, feed traces, and full message bodies are opt-in.
- Terminal text reads are bounded and marked untrusted.
- Worktree mutations require a repository visibly represented in ForkTTY.
- Team worker cleanup only closes current-runtime launch-owned disposable panes.
Designed for local trust
ForkTTY uses a local Unix socket and stdio MCP bridge rather than a network service. The security model assumes same-user local automation and avoids hidden remote control planes.
Questions
What can ForkTTY MCP tools inspect?
Can MCP tools send terminal input?
Is ForkTTY MCP network-exposed?
Explore related ForkTTY pages
Get the alpha build
AppImage and .deb packages are published on GitHub Releases for Linux x86_64.
View releases