Zoran

Your agents know how to reach you.

Zoran watches your local Claude Code and Cursor sessions. When a session needs a human — a permission to grant, a deploy waiting, a question only you can answer — your real phone rings. Press 1 to allow, 2 to deny. Hang up, go back to your life.

No screen, no notifications to miss. A phone call.

Install

pip install zoran   # or: pipx install zoran
zoran init

zoran init does everything: registers your device, installs the hooks into Claude Code (~/.claude/settings.json) and Cursor (~/.cursor/hooks.json) without touching your existing hooks, starts the daemon as a background service (launchd on macOS, systemd on Linux), and opens your dashboard to set your phone number. Nothing to keep running in a terminal.

What it feels like

• An agent asks for a risky permission → your phone rings, you press 1 or 2.
• A task finishes and the agent is waiting on your word → your phone rings.
• You're away and curious → call back. A voice tells you what's moving, what broke, what's waiting on you.
• An agent is going off the rails → say "freeze". It stops.
• Missed the call? You get an SMS, and YES/NO by text works too.

Your code stays home

The daemon runs on 127.0.0.1 only. Transcripts are read locally, on demand, and never stored or synced. What leaves your machine: session metadata and an 80-character tool preview, redacted before it leaves. The cloud exists so your phone can ring — it never sees your source. Details: zoran.run/privacy.

If the cloud is unreachable, hooks fail open: your agents keep working as if Zoran wasn't there.

Commands

Local dashboard: http://127.0.0.1:4090 · Cloud dashboard: zoran.run/app

Zoran is a product of Polymerix Labs Ltd, London. Support: support@polymerix.io