Get started
From an empty machine to an agent that reaches your phone, in three steps.
Zeph joins two things: the machine your coding agent runs on, and the phone in your pocket.
Start with the machine. Signing in there is also what creates your account, so there is never a credential to carry from one device to the other.
1. Set up the machine
npm install -g @zeph-to/cli
zeph installzeph install opens a browser sign-in. Use Google or Apple — if you have never used Zeph, that
first sign-in is also the sign-up. Approve the connection and the web app hands the CLI an API
key and a hook, which the CLI writes to ~/.zeph/config.json. Nothing to copy, nothing to paste.
The CLI then lists the AI agents it found on the machine and asks which ones to wire up. It installs rules, hooks, and MCP configuration for the ones you pick, sends a test push, and finishes:
✓ Test push sent: push_01J...
Done! Restart your agents.Remember that test push. It is how you will know step 2 worked.
No browser on this machine? On an SSH box or inside a container, run zeph install somewhere
that has one, then pass the two values from its ~/.zeph/config.json:
zeph install --key ak_... --hook hook_...2. Pick where it reaches you
You need at least one place to receive. Any of these works, and they all answer an agent's question with the same buttons — pick one now, add the rest later.
| Where | Get it | |
|---|---|---|
| iPhone, iPad | App Store | Reaches you away from the desk. This is the one the product is built around |
| Android | Google Play | Same |
| Chrome | Chrome Web Store | Fastest to add: its Sign in button reuses the browser session step 1 just opened |
| Any browser | app.zeph.to | Nothing to install |
Sign in with the same account you used in step 1. On a phone, allow notifications when the app asks — that permission is what lets your agent reach you while the screen is locked.
The test push from step 1 is already waiting at the top of your feed. Seeing it there is the confirmation that both ends are on the same account and the round trip is live.
3. Restart your agents
Agents read their hook configuration at startup, so a session that was already open when you ran
zeph install does not have it yet. Quit and reopen Claude Code, Codex, Cursor, or Gemini. The
next thing that agent finishes will reach your phone.
How loud it will be
Notifications fire for every session of each agent you wired up, not only sessions launched
through zeph cc. In Claude Code the default is quiet: you are pushed when the agent asks you
something and when a session finishes, not on every turn.
| Command | Effect |
|---|---|
/zeph-normal | push on every turn that did real work |
/zeph-loud | push on every turn |
/zeph-mute | full silence, current project |
/zeph-status | show what is in effect |
See Claude Code Plugin → Push Modes for the full dial.
If something looks wrong
zeph verifyIt checks installation health across every detected agent and reports what is missing. Add
--ping for a live API call.
Where to go next
- CLI & SDK — push from any script, and drive a live session from your phone.
- MCP Server — tools your agent calls on its own: ask a question, send a file, copy to your clipboard.
- Claude Code Plugin — hooks and skills, already installed by step 1.