Claude Code, Codex, Gemini CLI and your own agent commands, grouped by the folder they work in. See at a glance which session is working, which is idle, and which one needs you.




hangar command, within set limits.



Shows how many sessions need you, or how many are working. Its panel lists every session and your Claude and Codex usage.

Ten presets or your own background, text and accent colours, for one session, its folder or all of them. Tell sessions apart at a glance.
Each terminal runs in a small helper, so quitting or updating Hangar leaves every turn running. Only closing a tab ends it.
A session's subagents appear under it while they work. Click one to watch its transcript.
Buttons for the folder's project: build.sh, Xcode with a destination, Swift packages, package.json scripts or your own commands.
⇧⌘C shows the folder's changed files and diffs, with Commit and Commit & Push. Suggest drafts the message.
Your Claude and Codex session and weekly limits at the bottom of the sidebar, with when they reset.
Press both Option keys and a picture of your screen lands at the prompt of the session in front, ready to send.
The hangar command lets one session ask another, like "ask the Codex session to review this". Exchanges are capped so they can't loop.
An iPhone app is on the way.
Every key is listed in Settings › Shortcuts.
Hangar has no server and no account, and collects nothing. The agents you run talk to their own services, as they do in any terminal. Privacy policy →
hangar command talk over local sockets only you can open.Claude Code, Codex and Gemini CLI are built in, and you can add any other command-line agent in Settings › Providers. Live status, subagents, past conversations and usage are read for Claude Code and Codex; other agents run as plain terminals.
No. Hangar has no server and no account, and everything it reads stays on your Mac. The one exception is one you start: Suggest in the changes panel runs your own Claude Code with the folder's diff, so it goes to Anthropic under your Claude subscription. See the privacy policy.
They keep running. Each terminal lives in a small helper process, and the next launch reconnects with the screen intact. Closing a tab ends its session; a restart puts tabs to sleep, and clicking one resumes its conversation.
Yes, with the hangar command on the PATH of every session Hangar starts. Messages are marked as coming from another session, and exchanges are capped (by default 6 between two sessions and 20 from one session per 15 minutes).
A Mac with Apple silicon and macOS 26, plus the agents you want to use, installed and signed in. A plain shell works without any.
Nothing. Hangar will be free and open source once it's released.
A signed download, and the source code, arrive with the first release.