While you're away
Your desk was never the point.
Hand off the work and go live your life. Your agents run in your absence — nothing stalls waiting on you, nothing needs a human watching a terminal. You left the chair; the work didn't stop.
You don't check on your agents — they call you. When something's worth your attention, it comes to you by voice, hands-free, wherever you happen to be.
When it's worth it
When it counts, it calls.
A decision can't wait. A job just finished. Your agent reaches you the way you can answer from anywhere — a native incoming call. Easy to take, easy to dismiss. Nothing interrupts you that isn't worth it.
Calls, not nags
Requests arrive as native incoming calls on your lock screen — even with the app closed. Dismiss one and it backs off — you can configure how aggressively.
- Nowit rings
- 10 mintries again
- 30 minonce more
- 2 hrlast try
- Thenit stops
Hands-free, by voice
Paigy reads the request aloud; you answer out loud and get back to whatever you were doing. When a choice is visual, it shows you the image or design to pick from.
Private by design
Paigy never listens in the background — audio is processed only during a call you choose to answer. A constraint, not a feature.
The call is the mechanism — not the habit.
No new app, no new habit. It rings like a real phone call, and only when it has to.
And you decide how engaged to be — change it whenever. Let the agent judge what's worth a call, make every notification ring, or go fully Silent so nothing does and it all waits in your inbox until you're ready.
Switch any time, from anywhere — even mid-task.
How it works
Four steps, then go.
Pair an agent
Add the Paigy integration to your agent and approve it — a quick one-time step.
Tell it to reach you
Ask your agents to call when they need a decision, or to tell you it's done.
Go live your life
Leave the desk. Your agents keep working while you're away.
Answer, or don't
Decide by voice when it calls — or dismiss it and handle it later.
Yours to control
Nothing reaches you that you didn't allow.
- Connect or disconnect any agent at any time.
- Choose what can ring you — ring, banner, or stay quiet in your inbox.
- Private to you — your messages and transcripts are never shared between users.
- Erase anytime — a single notification, or your entire account and all its data.
Docs & guides
Stop babysitting the terminal.
Eight short guides — one per problem that brings people here — with the exact commands, and what actually happens on your phone.
Get a phone call when Claude Code needs approval
The agent hits a decision it can't make alone; your lock screen rings like a real call. Answer by voice, and it gets back to work.
Read the guide →A quiet inbox for everything your agents say
Agent chatter stays out of Slack. Updates settle silently in one inbox — only what's worth a ring becomes one.
Read the guide →Separate identities for Claude, Codex & Antigravity
One setup command gives every agent on the machine its own identity — its own name, its own voice on calls, its own leash.
Read the guide →Run agent sessions without a terminal window
A host service keeps this machine reachable, so your phone can start and steer sessions with nothing open on screen.
Read the guide →Answer your agent's questions from your phone
Yes/no, pick-one, multi-select, rank — plus images and safe HTML previews when a choice is visual. Tap it, or say it.
Read the guide →Never lose a long-running job
Agents promise a callback — when it's done, when it's blocked, or at a time you name — and Paigy makes the promise fire.
Read the guide →Decide when an agent may ring you
One dial: let the agent judge what's worth a call, ring for everything, or go silent and let it all wait for you.
Read the guide →Voice, without background listening
The mic is live only during a call you answered. Nothing listens in the background — by construction, not by policy.
Read the guide →Get started
Install in 2 minutes.
One command, one scan. It pairs this computer with a QR code, gives each of your agents (Claude Code, Codex, Antigravity) its own identity — no pairing codes — and leaves a host running your phone can launch sessions on. It only touches agents you already have, and re-running is always safe. Your agents, your subscriptions, your keys — Paigy is just the phone line.
curl -fsSL https://paigy.ai/install | sh
Using Claude, Codex, or a specific IDE? Pick yours for the exact steps.
One setup command pairs this machine by QR and gives Claude its own identity — no pairing codes. The plugin adds skills and hooks on top.
-
1
Set up this machine (one QR scan — no pairing codes)
npm i -g @paigy/harness && paigy-harness setup -
2
Add the Paigy marketplace
/plugin marketplace add paigy-ai/mcp -
3
Install the plugin (skills + hooks)
/plugin install paigy -
4
That's it
Setup already paired this machine and gave Claude its own identity — open the Paigy app to name it and pick its voice, and your agents can start reaching you by text or voice.
-
5
Optional: have your agent nudge you if you go quiet
Paste this into Claude Code and it re-pings you through Paigy whenever you haven't replied to its question — so a wait never quietly stalls.
/loop 15m If I haven't answered your question, notify me again via Paigy
Add Paigy to Codex, then pair your phone once. Codex can call or notify you whenever it genuinely needs input.
-
1
Set up this machine (one QR scan — no pairing codes)
npm i -g @paigy/harness && paigy-harness setup -
2
Add the Paigy marketplace
codex plugin marketplace add paigy-ai/mcp --ref main -
3
Install the Paigy plugin
codex plugin add paigy@paigy-aiStep 1 already paired this machine. Start a new Codex session and it can reach you — get the iOS app or sign in at paigy.ai to receive messages.
Add Paigy to Google Antigravity — same standard MCP server, same two minutes.
-
1
Run pairing and auto-configuration
npm i -g @paigy/harness && paigy-harness setupRun this in your terminal. It will pair your phone and automatically register the MCP server in your Antigravity configuration. Approve on your phone, then sign in at paigy.ai to start receiving messages.
Paigy is a standard MCP server — no Claude-specific code anywhere, verified over the raw protocol with a non-Claude client. It works with any MCP-compatible tool, including local-model setups: Cline, Continue.dev, Zed, Goose, mcphost, and anything running against Ollama, LM Studio, or llama.cpp.
-
1
Add this to your client's MCP config
Most GUI clients (Cline, Continue, Zed…) take this as JSON in their MCP settings — Cline's is
cline_mcp_settings.json, Continue's is~/.continue/config.json. CLI clients that support the standard MCP JSON format accept it directly too.{ "mcpServers": { "paigy": { "command": "npx", "args": ["-y", "@paigy/mcp@latest"], "env": { "PAIGY_AGENT": "local" } } } } -
2
Pair your phone
PAIGY_AGENT=local npx -y -p @paigy/mcp@latest paigy-mcp-onboardApprove on your phone, then sign in at paigy.ai to start receiving messages.
Heads-up: the tool descriptions ask your agent to pick between a few answer shapes (confirm, options, free text) based on context — Claude follows this reliably; smaller local models may be less consistent about it. Free text always works as a fallback.
Hand off the work. Stay reachable.