Skip to content
handupbeta
Download

handup setup and approval guides

The approval inbox for AI agents. Your agents ask before risky actions like migrations, releases and emails. You see exactly what they want to do and approve or deny from your terminal, desktop or phone.

handup runs on Linux and macOS computers, with an Android app for your phone. Windows x86-64 is a beta (CLI and desktop installer; see downloads). No iPhone app yet; a web inbox for iPhone and other browsers is included from v0.1.2 (not in v0.1.1 or earlier). Download it, or on Linux (glibc) or macOS install it from a terminal:

Terminal window
curl -fsSL https://github.com/gethandup/handup/releases/latest/download/install.sh | sh
handup setup

The Linux archive requires glibc. On Alpine, use the musl APK package instead of the install script.

On Windows, download the desktop EXE or CLI ZIP instead of running the install script. The desktop app starts the daemon; for the CLI ZIP, run handup serve in its own terminal.

On a Mac, brew install --cask gethandup/tap/handup works too. Packages and the desktop and Android apps are in downloads. You never need Git, Rust or the source.

handup setup starts handup in the background (on Windows, see downloads instead), connects every agent it finds (Claude Code, Codex, Cursor, omp) and installs the handup agent skill. It is safe to run again, and --dry-run shows what it would change. Restart your agents, then try it:

Terminal window
handup ask --title "Hello from handup" --wait

Approve it in handup inbox, in the desktop app (handup ui), or on your phone after pairing it over Tailscale. Releases work fully for a 14-day trial; handup license status shows the days left. See License and trial.

handup setup runs these steps; run them yourself to pick and choose:

Terminal window
handup service install # start handup in the background (not on Windows: run handup serve)
handup integrate all # connect every detected agent (--list shows what it found)
handup skill install # teach agents when and how to ask

integrate all creates missing agent configs (with backups). Claude Code and Codex get hooks plus MCP; Cursor and omp get MCP only. An existing omp tool-gating extension is upgraded, but a new one is opt-in with handup integrate omp. Only one agent?

Agents that don’t load skills can use handup prompt, which prints instructions to paste into AGENTS.md or CLAUDE.md (--agent claude|codex|cursor|omp tailors them). Run handup doctor if something doesn’t work, and handup help COMMAND for every flag.

handup is in beta. Agents submit a request with previews (a command, diff, file, image, JSON and more), wait, and receive the human decision with the content hash they must bind execution to. A deny is a normal answer with feedback, never a transport error and never permission to retry unchanged.

Command requests can also be run explicitly from the desktop app with Run or Run as admin. The agent receives run_result and must not run the command again. Phone and web clients never run commands: they review, decide, and can ask the desktop to stop a running one; see Desktop.

  • Agents: Claude Code, Codex, cursor, omp, MCP and shell/CI setup, with the approval contract agents must follow.
  • Any agent or custom harness: steps to add handup to your own agent loop, SDK app or framework over MCP, CLI or HTTP.
  • Email drafts: ask before sending, let the human edit the draft, then send it with your own mail tool.
  • Agent skill: print instructions with the installed CLI, or run handup skill install for the version-matched skill with complete offline docs.
  • Integrations: let other tools react to requests.
  • Remote access, the relay, the mobile app, the desktop app and the web inbox (included from v0.1.2): approve away from the terminal.
  • Rules: scoped allow rules, presence routing and the terminal inbox.
  • Cookbook: runnable recipes for canned email replies, sender routing, a policy auto-decider, forms, a publish gate and meeting replies.
  • Machine contracts: the daemon OpenAPI and the request and decision JSON Schemas.

Agents can read these docs as plain Markdown: append .md to any page URL (without the trailing slash, /index.md for this page) or request the page with Accept: text/markdown. /llms.txt indexes every page by section and /llms-full.txt holds the docs in one file (per-operation API pages are linked from the API overview instead).

Ask a question or reach us on the support page. The product site is gethandup.dev.

Every client opens the support page in your browser with the report kind, handup version and platform filled in; you add the description and, if you want a reply, your email.

  • Desktop app, phone app and web UI: Settings → Help & feedback → Report a bug or Request a feature. The keyboard shortcuts sheet (?) also links Report a bug, and so does the Something went wrong screen shown if a view fails to load.
  • Terminal: handup report (add --feature or --question). Over SSH, with --print or when output is not a terminal, it prints the URL instead of opening a browser.
  • To paste exact build details into a report, open Settings → About and press Copy: it copies the app version, commit, build date, platform, daemon version and license state as plain text.