Quick start
Start with dry runs so ForkTTY shows exactly what it would install before it writes Codex hook, MCP, or skill files.
forktty hooks setup codex --dry-runforktty mcp setup codex --dry-runforktty skills setup agents --dry-runforktty agent-health --jsonVisible 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?
Can ForkTTY resume Codex sessions?
Can Codex use ForkTTY through MCP?
Explore related ForkTTY pages
Get the alpha build
AppImage and .deb packages are published on GitHub Releases for Linux x86_64.
View releases