Skip to content
forktty_
Codex

A Linux-native workspace for Codex agents.

ForkTTY gives Codex a visible terminal workspace instead of a scattered set of shells. Keep Codex panes, git worktrees, status hooks, local MCP/socket context, and resume-ready session metadata in one place.

Quick start

Start with dry runs so ForkTTY shows exactly what it would install before it writes Codex hook, MCP, or skill files.

Check the Codex hook install
forktty hooks setup codex --dry-run
Check the Codex MCP registration
forktty mcp setup codex --dry-run
Check the shared Agent Skills target
forktty skills setup agents --dry-run
Inspect known agent sessions
forktty agent-health --json

Visible agent work

Codex runs in normal terminal panes, so every prompt, approval, test, and repository command remains visible. ForkTTY adds workspace focus, pane state, status metadata, and notification handling around the CLI without proxying model traffic.

  • Agent HUD rows show known Codex sessions, lifecycle state, current pane, and resume readiness.
  • Prompt-aware notifications surface approvals and blocked states without hiding terminal context.
  • Socket and MCP reads expose compact context for orchestrators before they act.

Worktree-based isolation

When multiple Codex workers touch code, ForkTTY can keep each branch in a separate git worktree workspace. That makes parallel implementation, review, and QA easier to inspect and less likely to collide.

Local-first by default

ForkTTY does not provide model access or copy your project to a hosted agent service. Codex keeps using your configured CLI and account; ForkTTY coordinates local panes, metadata, hooks, and notifications.

Questions

Does ForkTTY include Codex access?
No. ForkTTY is bring-your-own Codex CLI and subscription. It hosts and coordinates the terminal sessions you already run locally.
Can ForkTTY resume Codex sessions?
ForkTTY stores provider-neutral agent metadata and can preserve Codex resume context when the provider exposes enough session information. Agent health reports whether a saved session is ready.
Can Codex use ForkTTY through MCP?
Yes. ForkTTY exposes a local stdio MCP bridge backed by the same owner-only socket API used by the CLI.

Explore related ForkTTY pages

Get the alpha build

AppImage and .deb packages are published on GitHub Releases for Linux x86_64.

View releases