Skip to content

Agent Push Setup

The Inbox is powered by duckterm-hookd. Copy the personalized platform snippet from the app and run it once beside your agents; it installs, pairs once, wires supported hooks, and starts the service.

Before you start

  • DuckTerm installed on your phone or tablet (iOS / iPadOS 17+ on Apple devices)
  • A macOS or Linux machine where Claude Code / Codex / Gemini CLI / other agents run
  • Homebrew on macOS, or curl and systemd on Linux
  1. 1

    Copy your personalized setup snippet

    Open Settings → Agent notifications, choose macOS or Linux, then long-press the code block. The copied version includes the pair token and account id for this app.

    Get your ready-to-run command from DuckTerm

    This website cannot generate your private pair token. Install or open DuckTerm, then copy the prefilled command from Settings → Agent notifications.

    App Store
    Google Play
  2. 2

    Paste it once where your agents run

    Run the copied snippet on that machine. It installs hookd, pairs exactly once, registers supported Agent notifications, and starts the background service; no per-Agent setup is required.

    These examples use placeholders. Copy the personalized version from the app so its pair token and account id are already filled in.

    macOS

    Homebrew · Apple silicon & Intel 
    brew install ducksee/tap/duckterm-hookd && \
"$(brew --prefix duckterm-hookd)/bin/duckterm-hookd" setup --token <pair-token> --user <account-id>

    Linux

    Ubuntu, Debian & other systemd distros · arm64 / x86_64 
    curl -fsSL https://raw.githubusercontent.com/ducksee/duckterm-hookd-releases/main/install.sh \
  | DUCKTERM_PAIR_TOKEN=<pair-token> DUCKTERM_PAIR_USER=<account-id> sh
  3. 3

    Verify

    Run `duckterm-hookd status`, then use the Local push and platform-push buttons in Settings → Agent notifications. Future upgrades and service restarts keep this pairing.

    duckterm-hookd status

    Then use Settings → Agent notifications → Verify to send both a local test and a platform-push test. If they arrive on your phone, setup is complete.

Alternative for an existing install: pair by QR

If hookd is already installed and you prefer the camera, run the command below instead of the token pair command and scan the terminal QR in the app. Choose one pairing method; do not run both. Upgrades and service restarts keep the saved pairing.

duckterm-hookd pair --qr

What gets hooked

hookd verifies workflows for Claude Code, Codex, Grok Build, Antigravity, Cursor, OpenCode, Pi, Devin, Droid, Qoder, Amp, and Gemini CLI. Contract v1 defines seven decision schemas; six installed adapters currently carry phone decisions. OpenCode reports lifecycle status today while its permission-reply adapter remains pending. Grok Build uses its own hook system and a supported global hook source.

Claude Code Codex Grok Build Antigravity Cursor OpenCode Pi Devin Droid Qoder Amp Gemini

What leaves your machine

hookd builds notification previews from Agent hook events and transcripts; text or code from prompts and output can appear in them. Approvals, replies, and Live Preview or image fallback can also pass through the relay, while terminal traffic remains direct. SSH credentials are never sent to our servers. See the Privacy Policy for storage and retention details.

Privacy Policy

Trouble?

Check the Support page for common issues, or email us — we answer fast.

Support & FAQ [email protected]