A terminal designed to bea browser for agent sessions

A Mac terminal built around code agents. Many sessions in one window, naming and resume that work across Claude Code, Codex, OpenCode, and Hermes, folder chips that group by working directory, and the Mac-native rendering you expect. Quit the app and your sessions are still there tomorrow.

A chat UI guesses what you want to see and hides the rest. Agent output is big, and everyone's important two lines are different — so the guessing always loses something you needed. A terminal shows everything and lets your eyes do the filtering. That's calmer, not busier. And the details a friendlier UI hides are the details you'd have learned from.

Every tab is pinned to a stable ID injected into the agent's environment. A bundled shell snippet plus the agent's own session-start hook keep a marker file on disk. When you relaunch the app, the marker tells Push which agent to resume and which session ID to pass — and you land back in the conversation. Crash-safe via atomic marker writes; survives Sparkle auto-update; tolerates working-directory drift.

Claude Code is the deepest integration today — auto-resume, /clear handling, theme-respect on appearance changes. Codex, OpenCode, and Hermes are all first-class: their session storage is read for history, their resume command shape is invoked correctly, and their tab titles are normalized. Any other shell or CLI works as a normal terminal — you just don't get the agent-specific affordances unless we've integrated it.

Yes — push, and it ships inside the app rather than as a separate install. It’s how a session tracks itself as an issue, opens the next tab, hands its work to a different agent, reads another tab’s output, and reports back when it’s done. The /push skill is preinstalled for Claude Code, Codex, OpenCode, and Hermes, so the agent in the pane already knows the verbs — nothing to configure. You run the same commands yourself: push status for the workspace pulse, push track to turn the session you’re in into a tracked issue, push --help for the rest.

Usually they mean the layout — panes, working directories, a window restored. Push means the work: the conversation resumes through each agent's own session store, the issue keeps the history, and the status is still true after a real shutdown, a reboot, or a week away. A restored directory tells you where you were; a resumed session tells you what you were doing.

No — the tracker got smaller because its user changed. Human trackers are elaborate (Triage, Backlog, In Review, Blocked…) because status was always a coordination protocol between people. An agent doesn't negotiate priority; it runs or it doesn't. So Push has three statuses — active, done, archived — and the only one that exists for you, waiting on you, sets and clears itself: the agent opens an approval, the issue computes in-review, you answer, it's gone.

tmux is great for surviving a flaky SSH connection on a remote Linux box. The problem here is different — you're running many agents locally and need to know which one needs you, where it left off, and how to pick it up tomorrow. That requires reading what's inside each pane (session IDs, agent transcripts, hook output), which a terminal-agnostic multiplexer is designed not to do. Push reads what's inside the pane and treats agent panes specially. Different bet, different ceiling.

No. Mac-side data lives in ~/.push/. Agent transcripts stay where the agent put them — Claude's JSONL files in ~/.claude, Hermes' SQLite in ~/.hermes, and so on. Push reads them locally to render history and never uploads them. Auto-updates check a signed feed at releases.pushto.do. The agents themselves make their own API calls to whatever model you pointed them at — that's between you and them.

Mac-only today. The native rendering, the libghostty palette pipeline, and the macOS-specific keyboard conventions are load-bearing for the experience we're shipping — porting them isn't a flag flip. If you need a cross-platform multi-pane terminal for agents, a modernized multiplexer is a different shape that fits Linux better.

Closed-source, signed, notarized binary today. Documentation around the macOS architecture and integration playbooks is being opened up. No commitment yet on the source itself.

The Mac app is free — the terminal, the agents, and the orchestration are not gated. Voice todos are unlimited. Push includes 100 minutes of recording each month; that one guardrail protects the cost of transcription, and reaching it never opens a paywall. Full pricing.