Support
Get in touch
- Testing Pulse through TestFlight? Open TestFlight, choose Pulse and tap Send Beta Feedback, or take a screenshot while Pulse is open and share it as feedback. It goes straight to the maker.
- On the early-access list? Reply to any e-mail you received from the list. A person reads it.
- Found a security problem? Use one of the two routes above, and keep the details out of public places. More under Security.
It helps to mention your iPhone or Mac model, the iOS or macOS version, and what you expected to happen.
What Pulse needs
| Part | Requirement |
|---|---|
| iPhone | iOS 26 or later. Pulse is an iPhone app; there is no iPad version. |
| Mac | macOS 15 or later, with the Pulse Mac app running. The Mac app is the part that types your answers and opens new sessions. An answer it does not pick up expires — after an hour for a message, after 15 minutes for a permission or an option — and you get a notification that it was not delivered. |
| Terminal | iTerm2. Claude Code has to run in iTerm2: that is where Pulse finds a session's tab and types into it. Other terminals are not supported yet. |
| Claude Code |
With Pulse's hooks installed on the Mac (hooks/install.sh from the
Pulse repository). They report when a session finishes, fails or waits for you,
each tool step, and the usage your status line shows.
|
| Accounts |
Pulse knows accounts the way its maker set them up: four Claude Code config
folders, called cc1 to cc4, each started with a shell
command of that name. Starting a session from your phone and the account
overview only work with those four for now. Notifications and replies work with
a standard Claude Code set-up too.
|
| Language | The apps are in Dutch for now, and so are the buttons on a notification and the question macOS asks before Pulse may type into iTerm. Only the first-run setup also comes in English: it follows your system language. |
| Server |
A Pulse server and its device key. The apps connect to
pulse.synccy.com unless you enter another address, and every
device signs in with the same key — see
the device key.
|
Setting up
The first time it opens, Pulse walks you through it: allow notifications, let Pulse type into iTerm (macOS asks once), connect to your server with the device key, and send yourself a test notification through the whole chain — your server, Apple Push, your device.
If something does not work
No notification arrives
Send a test notification from Pulse's settings. It travels the same way as a real one and tells you where it stopped: at your server, or at Apple Push. If the Mac cannot reach the server, it shows a local notification instead and sends the event along with the next one.
An answer does not reach the terminal
Check that Pulse is open on the Mac and that iTerm is running. macOS has to allow Pulse to control iTerm: System Settings → Privacy & Security → Automation. Pulse does not need Accessibility or Screen Recording; it only talks to iTerm, through AppleScript.
The setup says the hook was not found
Run hooks/install.sh on the Mac where you use Claude Code. Pulse looks
for it in ~/.config/pulse.
Frequently asked
What is Pulse?
A companion for Claude Code on your iPhone and Mac. When a session finishes, fails or stops to ask for your permission, Pulse sends a push. You can follow a running session step by step, and answer from your phone: your Mac types the answer into that session’s iTerm tab.
Can I get it today?
Not yet. Pulse runs every day on its maker’s own iPhone and Mac, but there is no App Store or TestFlight build for anyone else yet. Leave your e-mail address and you’ll hear when early access opens.
What do I need?
A Mac where you run Claude Code in iTerm2, an iPhone, and Pulse on both. The Mac app is the part that types your replies and opens new sessions, so it has to be running. Other terminals aren’t supported yet. The apps are in Dutch for now; only the first-run setup also comes in English.
How does my answer reach the right session?
Every event knows the iTerm session it came from. Tap Allow and your Mac presses Return in that tab; Deny presses Escape; a number picks that option; a typed message is entered and sent. A reply that can’t be delivered expires — after 15 minutes for a permission or an option, after an hour for a message — so an old tap never lands in a session that has moved on.
Does Claude Code wait for Pulse?
No. The hooks run asynchronously, so a session never waits for a push to go out. If the server can’t be reached, your Mac shows a local notification instead and sends the event along with the next one.
What gets sent, and how long is it kept?
Your prompt and Claude’s last message (both shortened), the session’s name, project folder, account and status, and one line per tool step — for a shell command, the command itself. Steps are deleted after two days and usage snapshots after seven; the notification history keeps the latest 2,000 events. The privacy page has the full list.
I use more than one Claude account. Does that work?
Yes — that is what it was built for. Pulse reads the usage your Claude Code status line already reports, and shows per account how much of the five-hour session and the weekly limit is used, and which account has the most room left. For now it knows accounts the way its maker set them up: four Claude Code config folders, called cc1 to cc4. That overview only lists those four; notifications and replies work with a standard Claude Code set-up too.
Can I start a session from my phone?
Yes, with one condition for now. Pick a project folder and an account, and your Mac opens a new iTerm tab there and starts Claude Code with the command for that account — cc1 to cc4, the shell shortcuts its maker uses. Without those commands a new session doesn’t start yet. If the Mac doesn’t pick the request up within ten minutes, it expires.
Why not just a push from a webhook?
A plain push tells you something happened. Pulse keeps one notification per session — a new status replaces the old one instead of piling up — shows what the session is doing while it works, and closes the loop: you answer, and the answer lands in the right tab.
Is Pulse made by Anthropic?
No. Pulse is an independent project by one developer. It uses the hooks and status line Claude Code offers to everyone, and it isn’t affiliated with or endorsed by Anthropic.
Your data
What Pulse sends to its server, what passes through Apple, and how long each piece is kept: Privacy. What you may and may not do with Pulse and its server: Terms of Use.