Workspaces stay focused on terminals.
The GTK workbench keeps projects, tabs, split panes, unread state, and notifications visible without adding a second orchestration product beside the terminal.
❯ forktty tree
Linux-nativeOpen sourcev0.2 alphaforkttyThe Linux workspacefor coding agents.
Run Codex, Claude Code, Pi, Antigravity, OpenCode, Grok Build, and shell tools side by side in one native GTK/Ghostty workbench. Keep panes, worktrees, notifications, and resume-aware status visible.
Ghostty panesWorkspacesGit worktreesLocal socket
AppImage and .deb builds for Linux x86_64 alpha. Verify SHA256SUMS before running.
Capabilities
Built for agent workspaces
ForkTTY keeps terminal panes, agent sessions, and git worktrees visible without moving project data off your machine.
Agent HUD, not scrollback archaeology.
Optional hooks for Codex, Claude Code, Antigravity, and OpenCode publish session ids, cwd, lifecycle, and last activity so the GTK HUD can focus or resume an agent.
❯ forktty agents
Worktrees are first-class workspaces.
Each task gets an isolated git worktree workspace: create, attach, merge, remove, with dirty-state protection and setup/teardown hooks.
❯ forktty worktree-status
A small local automation surface.
The owner-only JSON-RPC socket backs the CLI for workspace, pane, focus, terminal reads, notifications, worktrees, project actions, and thin agent lifecycle controls.
❯ forktty capabilities
Ghostty terminals with native Linux polish.
GTK4/libadwaita in Rust around Ghostty's embedded terminal widget: split panes, tabs, retained scrollback, native selection and clipboard behavior, OSC links, visual bell, and desktop notifications.
Local-first by design.
Terminal contents, project data, and session files stay local. The default telemetry is limited to an anonymous daily usage ping and a once-a-day GitHub update check, both shown at first launch and controlled by a toggle. The Unix socket is owner-only, command execution is argv-based, and agent CLIs keep their own credentials.
Use cases
Agent workflows with dedicated context
Start from the workspace you need: Codex, Claude Code, external MCP tools, git worktrees, Agent HUD, Ghostty panes, or PTY persistence.
Codex
Run Codex in a Linux-native ForkTTY workspace with Ghostty panes, git worktrees, notifications, optional hooks, and safe resume flows.
Claude Code
Run Claude Code in visible Ghostty panes with workspace navigation, git worktrees, notifications, optional hooks, and resume metadata.
External MCP
Run MCP-enabled agent clients and external MCP servers as normal processes in ForkTTY terminal panes; ForkTTY itself exposes a small local socket API.
Git worktrees
Use ForkTTY git worktree workspaces to isolate parallel coding agents, branches, setup hooks, merges, removes, and repository state.
Agent HUD
ForkTTY's Agent HUD shows optional lifecycle metadata, current pane, freshness, resume readiness, and risky permission modes.
Ghostty terminal
ForkTTY embeds Ghostty terminal widgets in a native GTK4/libadwaita workspace with tabs, splits, scrollback, links, clipboard, and notifications.
PTY persistence
Optionally keep plain terminal processes alive across ForkTTY UI restarts with local dtach-backed sessions.
Parallel panes
Run multiple coding agents visibly in ForkTTY tabs, split panes, and git worktree workspaces without a built-in team or workflow engine.
Alternatives
Compare ForkTTY's Linux-native GTK/Ghostty workspace approach with terminal multiplexers, editor terminals, and orchestration-focused agent tools.
Latest release
Get ForkTTY
AppImage
Portable build — recommended
forktty-0.2.0-alpha.19-x86_64.AppImage
77.2 MB
.deb package
Debian / Ubuntu
forktty_0.2.0.alpha.19_amd64.deb
41.8 MB
Quick start
$ sha256sum -c SHA256SUMS --ignore-missing$ chmod +x forktty-*.AppImage$ ./forktty-*.AppImageBuild from source— Rust 1.96+, GTK4 / libadwaita, Git, Zig
$ git clone https://github.com/Lucenx9/forktty.git$ cd forktty$ cargo run -p forktty-ui-gtkEarly alpha: expect breaking changes between releases, and builds are unsigned — verify against SHA256SUMS. Linux x86_64 only. The AppImage is the primary portable download; the .deb is for Debian/Ubuntu. Packaged builds ship the GTK/Ghostty terminal runtime, while browser panes remain source-only behind the browser feature.
FAQ
Common questions
Does ForkTTY ship with an AI model?
No. ForkTTY is bring-your-own-CLI: you install the agent of your choice, authenticate with your own keys or subscription, and ForkTTY just hosts the PTYs. Nothing is proxied.
Which agents have first-class integration?
Every agent CLI works as a normal terminal process. Optional manual hooks for Codex, Claude Code, Antigravity, and OpenCode add lifecycle metadata for the Agent HUD and supported resume flows. Pi, Grok Build, shells, editors, and custom tools need no ForkTTY-specific integration.
Can I script or automate it?
Yes. The forktty binary speaks a bounded JSON-RPC-like API over an owner-only Unix socket for workspaces, panes, focus, terminal text, notifications, worktrees, project actions, remotes, and thin agent lifecycle controls. ForkTTY does not ship an MCP bridge; external MCP tools still run normally inside panes.
Does it really do git worktrees?
Yes. Workspaces can be backed by isolated git worktrees that ForkTTY creates, attaches, merges, and removes via native git2 operations — with dirty-state protection and optional .forktty/setup and teardown hooks.
Are browser panes included in the downloads?
No. The alpha AppImage and .deb are GTK/Ghostty terminal builds. WebKitGTK browser panes, browser profiles, history/bookmarks, and import flows remain source-only behind the browser feature for intentional testing.
Will there be a macOS or Windows build?
Not in alpha. ForkTTY is unapologetically Linux-first; portability isn't a near-term goal.
Is anything sent to a server?
Only an anonymous daily usage ping and an optional once-a-day GitHub update check, both on by default and one toggle to disable. The ping carries just a schema tag, app name, version, and date — no crash reports, analytics, identifiers, terminal contents, or project data. A first-launch dialog shows the toggle before anything is sent. Agent CLIs talk only to whatever endpoint you configure them to.