Otty
A native and beautiful terminal emulator
160 followers
A native and beautiful terminal emulator
160 followers
Otty is a native, GPU-accelerated terminal, designed for anyone who cares about the feel of every keystroke — minimal, fast, and beautiful. A terminal worth using on its own. And when you run several code agents like Claude Code or Codex side by side, Otty keeps it calm and clear — tuned for the agents you already run. Optimization, not complexity.
Free
Launch Team / Built With
CloudflareYour next app belongs on Cloudflare Workers. Deploy for free
Promoted
Session recovery, especially for Claude Code/tmux sessions, is the detail that would make me actually try switching terminals. Agent work is full of long-running context, so losing a pane is much more painful than it used to be. Curious how far recovery goes today: process state, scrollback, layout, or all of it?
All of it.
For Claude Code, Otty will run `claude --resume {your_session_id}` when recovery, similar for tmux. For other terminal commands, scrollback, layout is included. It can even go further -- recover commands you was running based on configs: https://docs.otty.sh/workflows/session-recovery#config-what-to-recover
GPU-accelerated rendering in a terminal is the kind of thing that sounds like over-engineering until you're actually running five agent processes in split panes and watching your old terminal stutter. The focus on agent-forward UX is a real differentiator. What rendering backend are you using for the GPU layer? And does the split pane model support custom layouts per workspace?
Ha — "over-engineering until you're running five agents" is exactly the moment it earns its keep. That's the whole reason it's there: when several agents are streaming output at once, pushing rasterization to the GPU keeps every frame smooth and leaves the CPU for the actual work, instead of the terminal choking on redraws.
Backend is Metal on macOS.
Splits are per-tab right now — each tab carries its own split layout. Not sure if "per workspace" is exactly what you mean, but if you're after saving and reusing custom layouts, you can save one with ⌘S and pull it back with ⌘⇧P. Is that the workflow you had in mind, or were you picturing named workspaces with their own layouts?
GPU-accelerated and designed to stay clean even with code agents running — that's a real differentiator. How does Otty compare to Ghostty on rendering performance and resource usage in your testing?
The performance is fast enough compared with ghostty -- https://docs.otty.sh/reference/performance
But it is not a controlled test env, just casual test.
A Mac-native terminal that's actually thoughtful about rendering is rare. We've spent time debugging unicode and escape code rendering bugs in iTerm configs that just don't exist in native apps. How's the AI integration scoped: is it a sidebar assistant, inline suggestions, or does it actually intercept command output to annotate it?
@retain_dev
Totally agree native pays off here — a lot of the weird escape-code/unicode breakage you fight in iTerm configs just doesn't happen when there's no config layer in the way. That said, I won't pretend Otty is bug-free on unicode — my coverage isn't as battle-tested yet, so there are probably edge cases (throw a weird emoji at it 😄) — but everything I've hit, I've fixed.
On the AI integration — honestly, none of the three. There's no built-in AI: no sidebar assistant, no inline suggestions, no output interception. Instead Otty is tuned to be the best place to run the code agents you already use (Claude Code, Codex, OpenCode…). More here: https://docs.otty.sh/agents/agents-overview
Every app is racing to bolt AI on right now, but setting up an API key in each one gets old fast. Think of Otty as BYOC — Bring Your Own Code agent. 😄
@abner_lee is it / will it be open - source ?
Love it!
Means a lot — built it for exactly this 🙏