Titan

-- see it work

Recorded in Titan, nothing staged: real Claude Code and pi sessions on a small timer app. Pick one, or let them play through.

-- why a terminal built around agents

Claude Code's TUI takes over a whole terminal: its own transcript, its own input box, its own spinners. Run three of them and you're flipping through tabs to find the one that's waiting on you. Titan runs Claude Code in its structured stream mode instead, so a session is a pane like any other, and Titan knows what each one is doing.

-- bring your agent

Use Titan's own Claude pane, the claude CLI you already know, or another coding agent such as pi or Codex. Each one runs in a pane, can open panes and drive the browser beside it, and stays out of the panes that aren't its own.

you Start the dev server and check the page
▸ Ran 2 commands
▸ titan_do new_split direction=right command="npm run dev"
▸ browser_navigate localhost:4173 · browser_click "Break"
The page loads and Break sets the timer to 05:00.
The dev server is still running in a pane on the right.

pomodoro ❯ claude
╭──────────────────────────────────────╮
│ ✻ Welcome to Claude Code             │
╰──────────────────────────────────────╯
  mcp: titan · browser_*, titan_do, titan_panes
> open the timer in the browser beside me

pomodoro ❯ pi
Start the dev server beside you with titan, open it in the
titan browser and click Break.
$ titan do new_split direction=right command="npm run dev"
$ titan browser navigate url=http://localhost:4173/
$ titan browser click ref=e3
Done.

pomodoro ❯ codex
$ titan actions
new_split direction=right|down [command=CMD] [folder=DIR]
read_pane pane=ID [lines=N]
titan browser <tool>: navigate, snapshot, click, type…

-- the claude pane

⌘N starts a Claude Code session in a folder you pick, drawn as a conversation with an input box of its own.

-- titan actions

Every command in Titan is a named action. Bind it to a key, run it from a shell with titan do, or let an agent run it. Pick an action to see each way to call it, and what Titan answers.

Needs remote-control = true in the config, except titan browser. titan actions lists every action, titan panes what's open.

-- agents keep to their panes

An agent can use the panes it opened and the ones you grant it. For any other shell, Titan asks you first, so an agent that was talked into it can't type into your ssh session or a shell with sudo still warm. Try it: pick a mode, then have pi type into each pane.

-- set it up

1. Install an agent. Claude Code for Claude panes, and pi or any other agent you like for shells. Without one, shells work as usual.
2. Open the config with ⌘,. It's ~/.config/titan/config, every setting written out and commented on first launch. Titan reads your Ghostty config first, so your font and theme carry over.
3. Save. Titan applies changes within a second, and a line it can't read shows in a bar with its line number.

-- keys

The defaults. Every one can be rebound, removed or turned into a sequence with keybind, and the menus show the new key as soon as you save.

-- and a real terminal

-- faq

Can I use pi or Codex instead of Claude?

Yes. Run them in a Titan shell. They drive Titan with the titan command (titan do, titan panes, titan browser), and Titan keeps them to their own panes as it does Claude. The Claude pane itself is for Claude Code.

Can agents type into my shells?

Not without asking. They can use the panes they open themselves and the ones you grant; for any other shell, Titan asks you first, and you can allow it once or for that pane. It's all off until you set remote-control = true.

Why only macOS?

Titan is a native Mac app: SwiftUI and AppKit for the window, Metal for drawing, Liquid Glass from macOS 26. Its terminal core, libghostty, runs elsewhere, but everything around it is written for the Mac. There are no plans for Linux or Windows.

Can I download it?

Yes: the latest release is a disk image, signed with a Developer ID and notarized by Apple. Open it and drag Titan to Applications. It needs macOS 26 (Tahoe) on Apple Silicon, and Claude Code for its Claude panes. Titan checks for updates once a day and installs them from the tab bar.

Where do I send feedback?

Titan is a personal project and I'd like to hear what you think. Open an issue on the releases repo: what works, what doesn't, what you'd want next.

Does it need an API key?

No. Titan runs the Claude Code that's installed, so sessions use the account it's signed in with and count against that plan as usual. pi and other agents use whatever they're set up with.

Does it change how Claude Code behaves?

Barely. It's the same CLI with your settings, skills and MCP servers. Titan adds a short note to the system prompt so Claude knows that pages show up in the feed, how to write paths that link, and, when you turn it on, that it can open panes.

Where are my conversations?

Where Claude Code keeps them, in ~/.claude/projects. Titan reads them for its history list and to resume sessions, and they work in the plain claude TUI as well.