Hangar starts programs on your machine and passes your input to them. This page describes what the app aims to protect against, what the released version does for that, where the limits are and how to report a vulnerability.
What Hangar aims to protect against
An agent or a tampered repository should not be able to run or reach anything through Hangar that you did not allow. That leads to these goals:
- A working folder, a profile or an update source does not make Hangar run code you did not ask for.
- The interface reaches only the parts of the app core that were explicitly granted to it.
- Secrets do not end up in logs, config files or saved terminal history beyond what the settings describe.
- An update is installed only if its signature checks out.
What Hangar does
Hangar starts programs as a list of arguments, never as a command line assembled for a shell. On Windows, update sessions and batch files do not look for programs in the working folder.
Secret variables of a profile are stored in the operating system's credential store, not in a file.
- Pasted text loses its control characters before it reaches the program.
- When Hangar itself pastes several lines from notes or snippets into a program that has not turned on bracketed paste, it asks first.
- Links in the terminal open only web addresses with http or https and local files and folders, no network or device paths. A file opens only with a harmless extension; Hangar shows any other in the file manager.
- Side windows such as the file viewer can call only the commands granted to each of them.
In team sessions, Hangar asks before an agent changes a file that another session or a teammate is working on. You answer once, for this file, or with an "Always" or "Never" rule for a file or folder of the project. Every automatic answer appears in the log. If no answer comes within ten minutes, Hangar declines. This applies to Claude Code, Codex CLI, OpenCode and Pi.
Team data is end-to-end encrypted. The server stores and forwards it but cannot read it. It does see who is in the team, which devices exist, when and how much is sent and who talks to whom. A new device joins the team only after an existing device has compared its safety number and confirmed it. Hangar connects to the relay only over wss, and over plain ws only to an address on this machine. Shared notes are stored encrypted in the repository.
Updates
Every update is signed. Before installing, Hangar checks the signature against the key in the app and rejects any file whose signature does not match.
The installer does not carry a code signing certificate yet, so Windows may show a SmartScreen warning the first time it runs. Every release includes a SHA256SUMS.txt file to check a download by hand.
Only the latest version receives security fixes. Hangar updates itself.
Limits
- Hangar is not a sandbox. Agents and shells run with your rights and run their commands themselves.
- Private sessions run without the questions of team sessions. New sessions start private by default.
- Please report vulnerabilities in the agent CLIs themselves to their vendors.
- More protections are in preparation. They will be listed here once the version that has them is released.
Report a vulnerability
Please do not open a public issue. Use GitHub's private vulnerability reporting instead. Include the Hangar version, your operating system, the steps to reproduce and the impact you expect.
You will get a first response within a week. Once a fix is released, the advisory is published with credit to you unless you prefer otherwise.
In scope are, for example, a working folder, profile or update source that makes Hangar run code you did not ask for, the interface reaching parts of the app core that were not granted, secrets leaking into logs, config files or saved history beyond what the settings describe, and any way around the update signature.