v0.11.0 is out

One window for every AI coding agent.

Hangar runs Claude Code, Codex CLI, Gemini CLI, Aider and any other terminal side by side. Every session keeps running in the background, with its full scrollback.

v0.11.0 · Nov 18, 2026 · 11.0 MB · Windows 10 1809+ / 11 x64 · Free & open source

New for Linux x64: AppImage · .deb · How to install

Hangar 0.11 with a Claude Code session whose backend and tester sub-agents stand as figures in the crew column beside its terminal, a second Claude Code session started as the security sub-agent wearing its figure and asking a question, Codex CLI working in its own worktree, Gemini CLI done and a PowerShell session; each sidebar row shows state, folder, branch, CPU and memory, the active one also its context use. Hangar 0.11 with a Claude Code session whose backend and tester sub-agents stand as figures in the crew column beside its terminal, a second Claude Code session started as the security sub-agent wearing its figure and asking a question, Codex CLI working in its own worktree, Gemini CLI done and a PowerShell session; each sidebar row shows state, folder, branch, CPU and memory, the active one also its context use.

Parallel without collisions.

Several agents in the same project, without one overwriting the work of another.

Team sessions need Git on your machine and a folder inside a Git repository.

  • Private or team

    A private session runs right in your folder. A team session gets its own Git worktree and is visible to your team. That way several agents change the same project at once. An agent started in a fresh worktree first checks for new upstream commits and asks before pulling them.

  • Asks before an agent steps in

    When an agent wants to edit a file another session is working on, Hangar holds it and asks you. Claude Code, Codex CLI, OpenCode and Pi run as team sessions; the check was measured live for each of them.

  • Remembers your answers

    Say "always" or "never" for a file or folder of a project, and Hangar answers for you from then on, with a visible log.

  • Warns about overlaps

    Hangar notices when two sessions change the same file or even the same lines, also across worktrees of the same repository.

  • Lets agents compete

    The arena gives one task to two to four agents, each in its own worktree from the same commit. Compare files, lines, time and tests, then take over the winner's changes, uncommitted.

  • Cleans up after itself

    When a team session ends, Hangar removes its worktree again unless it still holds changes.

Built for long agent sessions.

Everything a day with five agents in parallel needs, and nothing that gets in the way of your shell.

  • Sessions that keep running

    Every session runs in the background with its full scrollback. Output is batched with backpressure, so even heavy agent output never freezes the UI.

  • Sessions you recognize

    The sidebar groups by program or project folder, and an agent session takes its name from your first prompt. Each row shows its state, folder and branch. Hover it to see its last lines in their colors without switching to it.

  • One instruction file for all agents

    Write your rules once in HANGAR.md and Hangar hands them to every agent that accepts extra instructions (Claude Code, Codex CLI, Aider), without touching your repository.

  • Hand over to another agent

    “Hand over to …” in the session menu starts another installed agent in the same folder and inserts the last request, the changed files and your notes.

  • A calm home view

    The house button or Ctrl Shift H puts the sessions aside and shows a calendar of your commits over the last year. The sessions keep running.

  • Knows when an agent waits

    The sidebar shows which agent is asking. Add a sound, a desktop notification, a push to your phone (ntfy or Pushover) and a taskbar badge if you like, all quiet during the hours you choose. Ctrl Shift A jumps to the next one.

  • What changed when it is done

    When an agent finishes, a short notice names how many files it changed and opens them in one click. A local dev server an agent starts shows as a globe on its row that opens it in the browser.

  • Load at a glance

    A slim bar shows the machine's CPU, memory and GPU as small live graphs. Every session row shows its own load and, when it uses the GPU, its GPU load and memory (GPU values on Windows); a mark flags one that keeps a whole core busy or holds a lot of memory.

  • Picks up where you left off

    Sessions, order and scrollback come back after a restart. Agents that support it resume their last conversation.

  • Notes per project folder

    A tabbed Markdown notepad next to the terminal, saved automatically and tied to the working folder.

  • A real terminal

    xterm.js with truecolor, Unicode, OSC 8 links and bracketed paste on a real PTY (ConPTY on Windows).

  • Knows your agents

    A built-in catalog of 22 agent CLIs detects what is installed, shows the version and offers only what you can start. Updates run on request, in a visible session. Hangar never installs anything on its own.

  • Keys stay with your shell

    Ctrl plus a letter always goes to the program. Light and dark themes, 12 languages, keyboard-driven menus.

  • Signed auto-updates

    Every update is signed. Hangar refuses any file whose signature does not match the key built into the app.

  • Up to four sessions side by side

    Show two, three or four sessions at once, arrange them by dragging and resize them by dragging the lines between them.

  • A terminal that feels like an editor

    A click in the prompt line moves the cursor there without taking the agent's grey suggestion. Backspace or Delete removes marked text, also across the rows of a long, wrapped prompt, and Shift+Enter starts a new line instead of sending. Your last prompt stays visible above the terminal; a click jumps to its line. Web addresses, files and folders in the output open with one click.

  • Speak instead of typing

    Hold Ctrl Shift Space, speak and let go: the text lands in the prompt. Recognized on your own computer, nothing leaves it.

  • Workspace templates

    Save the running sessions as a template and start the whole set again later with one click.

  • Quick access

    Ctrl Shift P finds sessions, programs, files, recent commits, settings and every menu command. Ctrl Shift S searches the output of all sessions, Ctrl Shift M shows them as live tiles.

  • Review and commit in place

    The Changes tab lists the changed files, collapsed for an overview, and the recent commits. Stage, unstage or discard a file or everything at once, write a commit or ask the agent for a message, and click a diff line to send the agent a comment about it.

  • A timeline of agent steps

    After each agent step Hangar quietly saves your files, outside the repository. See the changes of every step and go back to any saved state.

  • A file viewer that keeps up

    Files open in their own window with syntax colors, a Markdown preview, images and a comparison with the last commit. While an agent edits the file, the view refreshes live.

  • Paste screenshots

    Copy a screenshot and press Ctrl V: Hangar saves the image and pastes its path, so the agent can attach it.

  • Snippets and broadcast

    Reusable text snippets with variables such as {{file}}, {{branch}}, {{selection}} and {{diff}}, saved from selected terminal text with a right click, and one message sent to several sessions at once.

  • Sub-agents as a tree

    The sub-agents of a Claude Code session appear as a tree below it, with what each one does, its run time and its tokens. One click shows a sub-agent beside the terminal, with recognizable keys and passwords masked.

  • Context at a glance

    Claude Code sessions show how full their context window is right in their row, for example 12 % · 123k / 1M.

  • Tokens and costs

    Tokens and estimated costs per session and per day for Claude Code, with a daily budget that tells you once when it is reached.

  • Your colors for every state

    Working, done, waiting and paused each get their own color, pulse strength and pulse duration, previewed live in the settings.

  • Profiles as files

    Programs, arguments, working folders and environment variables are plain configuration. Secret variables are stored in the operating system's credential store, never in a file.

  • Paths in the right form

    With a right click or a drag, a file's path lands in the terminal the way its program reads it: an @ mention for agents, a quoted path for PowerShell, cmd, Git Bash and WSL.

  • Your profile picture

    Your profile picture from your Hangar account shows in the app's sidebar. You upload it under Account › Settings.

  • Security, described openly

    What Hangar aims to protect against, what the app does for that, where its limits are and how to report a vulnerability: see the Security page.

New in Hangar 0.11.

Hangar for Linux, a connection test for your own server and 31 figures for your sub-agents, plus messages between projects, your crew beside the terminal and dictation on your own computer.

Scenes from Hangar

A message to your partner project

Link projects that belong together, such as an app and its website, on their project card. “Send to partner” in the session menu sends a message to the other project's agent session, with a header line naming the sender. If that agent is working, the message waits until it pauses.

The Send to partner dialog of a Gemini CLI session in the acme-docs project: a question about a refund status code written to the partner project shop, below it Webhook retries chosen among its three agent sessions, with Paste and Paste and send. The Send to partner dialog of a Gemini CLI session in the acme-docs project: a question about a refund status code written to the partner project shop, below it Webhook retries chosen among its three agent sessions, with Paste and Paste and send.

Agents write to each other

Agents in linked projects message each other with hangar-send. Nothing is pasted on its own: the message waits under the session row until you choose Paste, Paste and send or Discard. You decide what your agent gets to read.

A message from the partner project shop waiting under the Refund docs session row: the request to document the payment webhook retries, with Paste, Paste and send and Discard. A message from the partner project shop waiting under the Refund docs session row: the request to document the payment webhook retries, with Paste, Paste and send and Discard.

Sub-agents with figures and their own models

Settings › Sub-agents lists your Claude Code agents from ~/.claude/agents and your projects, and Codex CLI's own agent files. Each one wears one of 31 figures or your own image, also animated. Pick a model per agent and a default per program, start a session as a sub-agent (claude --agent) and provide the same crew to Codex CLI as well. New figures for marketing, sales and social media: agents with these names wear them automatically.

Settings › Sub-agents: the figure picker of the backend sub-agent open with all 31 bundled figures and the chosen one marked, above it a model per program, below it the developer sub-agent with its figure. Settings › Sub-agents: the figure picker of the backend sub-agent open with all 31 bundled figures and the chosen one marked, above it a model per program, below it the developer sub-agent with its figure.

Your crew beside the terminal

Running sub-agents stand as figures in a column next to their agent's terminal, each on a plinth with its name. The plinth's color shows the state (working, waiting for you, done), and a speech bubble says what the figure is doing right now, such as “Reading parser.rs”. A narrow window shows a strip of faces instead; the session menu shows or hides the crew.

The crew column beside a Claude Code team session: backend and tester working on blue plinths, security waiting for an OK on an amber plinth, each with a speech bubble, while the command guard asks about git clean -fdx above the terminal. The crew column beside a Claude Code team session: backend and tester working on blue plinths, security waiting for an OK on an amber plinth, each with a speech bubble, while the command guard asks about git clean -fdx above the terminal.

Dictation on your own computer

Hold Ctrl+Shift+Space, speak and let go: the text lands in the prompt of the active session. Speech is recognized locally, nothing is sent anywhere. Turn it on under Settings › Dictation.

A Claude Code session while the dictation key is held: the Listening pill with its level on the terminal and the dictated sentence in the prompt. A Claude Code session while the dictation key is held: the Listening pill with its level on the terminal and the dictated sentence in the prompt.

Check your own server step by step

If your team runs its own Hangar server, enter its address under Settings › Account. Test connection checks the account API, the relay and the live connection one after another and tells you what to fix when a step fails, such as a missing proxy rule. A link leads to the guide, and a note explains where your data then lives.

Settings › Account with the address of a self-hosted server: the link to the self-hosting guide, the note on where the data lives, and Test connection: the account API answers, the relay lacks its proxy rule (HTTP 404), the live connection is not yet tested. Settings › Account with the address of a self-hosted server: the link to the self-hosting guide, the note on where the data lives, and Test connection: the account API answers, the relay lacks its proxy rule (HTTP 404), the live connection is not yet tested.

Privacy in the team: your code stays in Git.

Hangar shares what the agents are doing, not what they write.

What your team sees and never sees
Your team sees Your team never sees
Your display nameFile contents and diffs
For sessions in shared folders: agent, title and stateYour e-mail address
The files those sessions change, with line numbersYour keys, tokens and environment variables
The tasks you reserveAnything from folders you do not share
  • End-to-end encrypted

    Everything you share is encrypted on your device. The team server stores and forwards it but cannot read it.

  • Devices are confirmed

    A new device joins only after a teammate, or your own other device, compares the safety number and confirms it.

  • You choose what is shared

    Sharing is switched on per project and per folder, never across the board.

  • Works without an account

    Hangar works fully without an account. Only the Team window needs one.

22 agent CLIs, detected automatically.

Plus any other program you add as a profile in profiles.toml.

  • Claude Code
  • Codex CLI
  • Gemini CLI
  • Antigravity CLI
  • GitHub Copilot CLI
  • Cursor CLI
  • Kimi Code CLI
  • Qwen Code
  • Kiro CLI
  • OpenCode
  • Aider
  • Goose
  • Crush
  • Pi
  • Oh My Pi
  • ForgeCode
  • Kode CLI
  • Codebuff
  • Cline CLI
  • Mistral Vibe
  • Droid (Factory)
  • Amp

See every agent in detail

Ready in three steps.

  1. Download the installer

    Windows: Hangar-Setup.exe. Linux x64: the AppImage or the .deb. All from the latest GitHub release.

    Download for Windows

    New for Linux x64: AppImage · .deb

  2. Run it

    Windows: It installs for the current user. Until the installer is code-signed, SmartScreen may warn on first start: choose More info, then Run anyway. Linux: make the AppImage executable with chmod +x and start it, or install the .deb with sudo apt install.

  3. Start an agent

    Open Hangar, choose Private or Team and start a detected agent or a terminal.

Platforms

  • Windows 10 1809+ / 11 x64Supported
  • macOS 13+Planned Notify me
  • Linux x64 Ubuntu 22.04+, Debian 12+New

Linux is new and needs glibc 2.34 or later (Ubuntu 22.04, Debian 12 or newer). For macOS, the code already builds and passes its tests in CI.

Work on projects together

The app stays free and open source. You only pay when more people work together in your projects: per seat, valid for all your projects, monthly or yearly, cancel any time.

  • Invite members and admins by email
  • No payment details, no expiry date

Good to know.

Is Hangar free?

Yes. Hangar is open source under the MIT license. Read the code, file an issue or build it yourself.

Does Hangar install agents for me?

No. It detects what is installed and shows when a newer version exists. Updates run only when you ask, in their own visible session.

How does Hangar update itself?

Shortly after start and every 6 hours it checks the latest GitHub release. One click downloads, verifies the signature and installs. Hangar asks before it restarts, because running sessions end.

Why does Windows warn on first start?

The installer is not code-signed yet, so SmartScreen does not know it. Choose More info, then Run anyway. App updates themselves are always signature-checked.

What about macOS and Linux?

Linux x64 is available since Hangar 0.11: as an AppImage that updates itself and as a .deb for Ubuntu 22.04, Debian 12 or newer. Linux support is new; if anything looks wrong, please report it on GitHub. macOS is planned, and the code already builds and passes its tests there.

Does Hangar need its own API key?

No. Hangar brings no model and makes no API calls of its own. Each agent uses its own account and talks to its own provider, exactly as it does in any other terminal.

Can I use Hangar alone?

Yes. Everything except the Team window works without an account.

Where are my settings and notes?

In your user profile (Windows: %APPDATA% and %LOCALAPPDATA%, Linux: ~/.config/com.feoren.hangar and ~/.local/share/com.feoren.hangar). Shared notes are the exception: they live encrypted in the project's .hangar/notes folder.

Bring all your agents into one hangar.

v0.11.0 · Nov 18, 2026 · 11.0 MB · Windows 10 1809+ / 11 x64 · Free & open source

New for Linux x64: AppImage · .deb · How to install