Otty is for developers who spend real time inside terminal-based coding agents. Codex, Claude Code, and OpenCode still run as their own CLIs; Otty wraps those panes with native terminal UI that understands when an agent is running, idle, finished, or waiting on you.
What makes a terminal good for agents?
A coding-agent terminal has to do more than render text quickly. It needs to help you coordinate long-running conversations, approvals, background work, and recovered sessions without forcing you to stare at every pane.
| Need | What Otty adds |
|---|---|
| See agent state | Tab badges for processing, task complete, and awaiting input. |
| Avoid babysitting | macOS notifications when an agent finishes or needs approval. |
| Keep work moving | Prompt Queue sends the next command when the pane returns to an idle prompt. |
| Write better prompts | Composer gives multiline editing, undo, image paste, and a floating input panel. |
| Resume old context | Agent History renders Codex, Claude Code, and OpenCode transcripts and can resume sessions. |
| Split exploration | Fork or branch an agent session into another pane or tab. |
| Recover after restart | Session restore can reopen agent panes and resume supported sessions. |
Otty does not replace your agent CLI
Otty does not run a proprietary agent. You keep using the CLI you already trust, such as codex, claude, or opencode. The integration is a small hook or plugin that lets the agent report state back to the terminal.
That boundary matters. The agent owns the conversation and model behavior; Otty owns the terminal surface, panes, notifications, history viewer, and recovery behavior.
Why native terminal behavior still matters
Agent work still produces ordinary terminal output: diffs, test logs, prompts, TUIs, command history, progress messages, and escape sequences. Otty keeps that path native instead of turning the terminal into an Electron wrapper.
On macOS, Otty uses a Metal-backed renderer and real terminal panes. It also keeps VT behavior central, including OSC-based protocols for links, shell integration, progress, notifications, and proposed agent metadata.
Best fit
Otty is a strong fit if your daily terminal includes one or more long-running agent panes, frequent approvals, parallel tasks, and restart-sensitive sessions.
It is especially useful when you want a terminal that treats agent status as UI state instead of asking you to infer everything from a blinking cursor.