Get a phone call when Claude Code needs approval

You hand off a refactor, walk away, and come back to an agent that stopped on step one to ask permission. Paigy ends that: when the agent needs you, your phone rings — a native call on the lock screen — and your answer sends it back to work.

How it works

Paigy is a standard MCP server that runs beside your agent. When Claude Code hits something it can't decide alone — a destructive migration, an ambiguous requirement, a deploy target — it reaches you through Paigy with a hard wait. That becomes a real incoming call on your iPhone, even with the app closed.

Answer, and Paigy reads the question aloud and listens. Say "staging", or "yes, ship it", and hang up — the answer lands back in the agent's session and it keeps going.

Can't take it? Dismiss. It backs off on a gentle schedule — 10 minutes, 30 minutes, 2 hours by default — then settles in your inbox. The schedule is yours to change.

Sessions launched through the Paigy harness go one step further: the agent's own permission prompts route to your phone automatically, and destructive ones escalate to a ring.

Other harnesses can badge a session needs input — some can even text you. Those channels tell you; none of them can take your answer. Paigy's call is answerable: your reply lands in the session, and the run resumes.

Set it up for Claude Code

Install the harness — it pairs this machine with one QR scan and configures every agent it finds:

Then add the Claude Code plugin, which teaches Claude when to call, when to leave a quiet note, and to keep waiting for your answer instead of stalling:

Works with: Claude Code, OpenAI Codex, Google Antigravity, and any MCP-compatible client — Cline, Continue, Zed, Goose, and local-model setups included.