Skip to main content

Horncall

One app to approve them all. Answer your AI coding agents' permission requests from your Android phone — Claude Code, Gemini CLI, GitHub Copilot CLI and OpenAI Codex CLI, on any number of computers.

This repository is the PC add-on (open source, MIT). It hooks into the agents' own, documented hook systems and forwards a permission question to the phone only while you switch it on (you're away from the desk). At the desk, everything works as before.

  • Guide: https://horncall.bitlionaire.me · phone app: Android (see the guide)
  • End-to-end encrypted: AES-256-GCM with a key made on your computer and handed to the phone only by QR code. The relay sees ciphertext.
  • The phone signs every decision (Android Keystore, ECDSA P-256); the computer accepts only answers signed by the phone it paired with. A stolen key file can read orders, but approve nothing.
  • Dangerous commands (rm -rf, force push, DROP TABLE, edits to secrets, hooks or CI…) get a red card with the reasons and need a long press.

Install

Pick one. All of them end with the same pairing step: setup shows a QR code to scan in the app, in the browser or, over SSH and on headless servers, right in the terminal (horncall pair draws it there too).

Claude Code plugin (Claude Code keeps it up to date):

/plugin marketplace add bitlionaire/horncall
/plugin install horncall@horncall
/horncall:approver setup

pipx / uv (a horncall command; hooks for every agent, Claude Code via its settings.json):

pipx install horncall        # or: uv tool install horncall
horncall setup

ZIP with a wizard (no Python tooling needed beyond Python 3.10+): download horncall-plugin.zip from the guide, unpack anywhere and run setup.cmd (macOS/Linux: sh setup.sh). It copies itself to the per-user program folder (%LOCALAPPDATA%\Horncall\app, ~/Library/Application Support/Horncall/app, ~/.local/share/horncall/app); the unpacked folder can be deleted.

By hand: see exactly what would be added, then paste it yourself or let it write:

horncall install gemini --print     # claude | gemini | copilot | codex | claude-statusline
horncall install gemini

What the install changes

Where What
~/.horncall pairing key, trusted phones, on/off mode, log (plugin/ZIP installs also a private venv)
Claude Code the horncall plugin, or (pipx) four hooks in ~/.claude/settings.json; optionally a status line for plan limits
~/.gemini/settings.json, ~/.codex/hooks.json, ~/.copilot/hooks/horncall.json Horncall hook entries, only for the agents you pick

Other settings stay untouched; the first change to a file leaves a *.horncall-backup copy. The setup wizard lists the files and asks before writing. No services, autostart entries or admin rights. Remove everything: horncall uninstall all (in Claude: /horncall:approver uninstall all).

Every day

Command
horncall on / /horncall:approver on leaving the desk — questions go to the phone (--hours 2 switches off by itself)
horncall off back — normal questions on the computer
horncall status pairing, mode, server, trusted phones, connected agents
horncall name "Shop backend" label this project's orders on the phone

Gemini CLI asks on its own first — start it with gemini --yolo (same as --approval-mode yolo) so only the phone asks. Codex CLI: open /hooks and enable the three Horncall hooks.

How it works

The agent runs a hook (horncall hook <agent>) on a permission request. While Horncall is off it exits at once and the agent shows its normal dialog. While on, it encrypts the request, publishes it to an ntfy relay (ours by default, any ntfy server works: horncall pair --server) and waits for the phone's signed answer, which it returns to the agent as allow or deny. Answering on the computer instead removes the card from the phone.

Development

python -m pip install -r plugin/requirements.txt pytest
python -m pytest

Issues and pull requests are welcome. Horncall is an independent project, not affiliated with Anthropic, OpenAI, Google or GitHub; their product names only describe compatibility. Contact: bitlionaire.me@gmail.com

Metadata

Release files for horncall 0.5.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for horncall 0.5.14
File Size Uploaded Provenance
horncall-0.5.14.tar.gz 57.8 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for horncall 0.5.14
File Interpreter ABI Platform
horncall-0.5.14-py3-none-any.whl Python 3 none any Details

Total release size: 106.2 kB

Release files / horncall-0.5.14.tar.gz

Download URL horncall-0.5.14.tar.gz
Size 57.8 kB
Tags Source
SHA-256 checksum
How to use checksums
53a5f38f5390e731b40891d197a39aa4cd9076544ee5e22e5dd9ccc7a69bc62d
BLAKE2b-256 checksum
How to use checksums
0536fcd4a662ae24e1f6795e884378cee45e648fb41197e0239dce3e209b6ea8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release files / horncall-0.5.14-py3-none-any.whl

Download URL horncall-0.5.14-py3-none-any.whl
Size 48.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
90d63c3a451b25e1203973d9f2cff1c8017b50ba49805c55023f4fd8f1bffc61
BLAKE2b-256 checksum
How to use checksums
0129324f7e1392d2d9676f2499fce92e37d0cb23d2dc2b3c4e210275e153e1a2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Security for horncall 0.5.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for horncall-0.5.14.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.5.14 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page