Linux-native terminalv0.2 alpha

forktty

Coordinate Codex, Claude Code, Pi, Antigravity, OpenCode, Grok Build, and shell agents from one Linux-native terminal. ForkTTY keeps tiled GTK/Ghostty panes, a visible router rail, git worktrees, local socket automation, MCP, and resume-aware notifications in one place.

Router railAgent HUDGit worktreesLocal socket

Download for Linux View on GitHub

AppImage and .deb builds for Linux x86_64 alpha. Verify SHA256SUMS before running.

ForkTTY on Linux showing a workspace sidebar, embedded Ghostty terminal, Router rail, and bottom workflow feed.

Capabilities

Built for agent workspaces

ForkTTY keeps terminal panes, agent sessions, and git worktrees visible without moving project data off your machine.

01Agent HUD, not scrollback archaeology.

Hooks for Codex, Claude Code, Antigravity, and OpenCode persist session ids, cwd, lifecycle, and last activity so the GTK HUD can focus, resume, and show compact loop state for an agent.

❯ forktty agents

02Worktrees 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

03Socket and MCP automation share one surface.

The user-local JSON-RPC socket backs the CLI and MCP server, so tools can plan task strategy with explainable router profiles, workflow-inferred last-known-good stickiness, and harness routing signals, stage or submit approved team runs, inspect panes, read context snapshots and terminal tails, manage worktrees, resume agents, and publish team status.

❯ forktty task-plan

04Ghostty 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.

05Local-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 workflow you need: Codex, Claude Code, local MCP, git worktrees, Agent HUD, Ghostty panes, PTY persistence, or team orchestration.

Codex

Run Codex in a Linux-native ForkTTY workspace with Ghostty panes, git worktrees, local socket automation, Agent HUD state, and safe resume flows.

Claude Code

Coordinate Claude Code in ForkTTY with visible Ghostty panes, provider-aware prompt submit, Agent HUD metadata, MCP context, and git worktree isolation.

MCP

ForkTTY exposes a local stdio MCP bridge for workspace context, terminal panes, agent health, git worktrees, notifications, and team orchestration.

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 coding agent lifecycle, current pane, resume readiness, risky permission modes, workflow loop chips, and prompt state.

Ghostty

ForkTTY embeds Ghostty-backed GTK terminal panes with split panes, tabs, retained scrollback, OSC links, notifications, and Linux-native polish.

PTY persistence

ForkTTY can keep plain terminal processes alive across UI restarts with optional dtach-backed PTY persistence, configured from Settings > Worktrees.

Team orchestration

ForkTTY coordinates multi-agent coding teams with visible workers, tasks, mailbox dispatch, provider-aware submit, final-state health, and workflow loop metadata.

Alternatives

Compare ForkTTY with terminal multiplexers, agent dashboards, and AI coding workspaces when you need Linux-native panes, git worktrees, MCP, and visible team orchestration.

Get ForkTTY

v0.2.0-alpha.18Published Jul 6, 2026Release notes SHA256SUMS

AppImage

Portable build — recommended

forktty-0.2.0-alpha.18-x86_64.AppImage

78.3 MB

Download AppImage

.deb package

Debian / Ubuntu

forktty_0.2.0.alpha.18_amd64.deb

42.7 MB

Download .deb package

Quick start

$ sha256sum -c SHA256SUMS --ignore-missing$ chmod +x forktty-*.AppImage$ ./forktty-*.AppImage

Build from source— Rust 1.96+, GTK4 / libadwaita, Git, Zig

$ git clone https://github.com/Lucenx9/forktty.git$ cd forktty$ cargo run -p forktty-ui-gtk

Early 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.

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?

Codex, Claude Code, Antigravity, and OpenCode have hook-driven status and persisted session metadata for the Agent HUD and resume flow. Pi is supported for team launch, provider capabilities, Agent Skills, and safe resume through its documented CLI; Grok Build is supported for team launch, provider capabilities, safe resume, and plan-mode review workers. Custom tools can still use the socket CLI.

Can I script or automate it?

Yes — that's a core feature. The same forktty binary speaks a JSON-RPC API over a user-local Unix socket and can expose it as a local stdio MCP server: list workspaces, read context snapshots or terminal text, inspect pane trees, split/focus/send text, manage worktrees, notify, resume agents, publish status, and operate team, workflow, feed, project-action, and remote-inventory control planes.

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.