Step away.
Stay in the loop.

Pulse — your Claude Code sessions, on iPhone and Mac

A push the moment a session finishes, fails or needs you. Follow it live, approve a command or answer a question from your phone — your Mac types it into the right terminal tab.

Pulse runs on its maker’s own iPhone and Mac today. It is not on the App Store or TestFlight yet — leave your address to hear when there is a build to try.

By joining you agree to get emails about Pulse early access and the occasional update — no spam, unsubscribe any time. See the Privacy Policy.

Early access · iPhone and Mac
checkout-flowsearch-indeximage-pipeline
>Ship the checkout flow to staging.
The checkout tests pass. I’ll push the branch so staging picks it up.
Bash(git push origin checkout-flow)
Bash command
git push origin checkout-flow
Push the checkout branch
Do you want to proceed?
❯1. Yes
2. Yes, and don’t ask again for git push commands
3. No, and tell Claude what to do differently (esc)
Pulse
cc1Opus 5.55 h62 %week54 %
cc2Sonnet 5.55 h18 %week31 %
cc4Fable 5.15 h91 %week77 %
Today
checkout-flow9:38cc1Waiting for permission· storefrontBash: git push origin checkout-flow
image-pipeline9:07cc1Done· storefront· 4 min 12 sResized 212 product images and the manifest.
nightly-report6:02cc4Done· ops-scripts· 1 min 48 sNightly report written: 3 jobs ran, none failed.
Yesterday
flaky-tests17:26cc4Failed· fieldnotes-iosThe run stopped: the usage limit was reached.
release-notes15:12cc2Done· atlas-api· 58 sDrafted the release notes from 31 merged changes.
Registered · pulse.example.com
Reply channel on: types into iTerm what you answer in Pulse or on your phone
Pulse
Good morning
Waiting on you
checkout-flowcc1Bash: git push origin checkout-flow
Accounts2 min. ago
cc1Opus 5.5Session62 %↻ 2 h 14 mWeek54 %↻ 3 d 6 h
cc2Sonnet 5.5most roomSession18 %↻ 4 h 2 mWeek31 %↻ 5 d 11 h
cc3no data yet
cc4Fable 5.1Session91 %↻ 1 h 19 mWeek77 %↻ 1 d 19 h
What do you want to work on?
iPhone
  • Every session, what needs you first
  • A notification when one finishes, fails or needs you
  • Allow, deny or answer from the chat
  • Usage per account, with reset times
  • Start a new session on your Mac
Mac
  • The latest events in the menu bar
  • Click one to jump to its terminal tab
  • Types your answers into the right session
  • Opens new sessions in iTerm
Pulse for iPhone and Mac

Two screens. One pulse.

The Claude Code sessions running on your Mac, on your iPhone and in the menu bar: what is working, what is done, and what is waiting on you.

The apps are in Dutch for now; the screens on this page show them in English.

Notifications

Know the moment it stops.

A notification the moment a session finishes, fails, or needs your permission or an answer. In Pulse every session is listed by its latest activity, with a dot that says where it stands.

One notification per session: a newer one takes the place of the one before it.

Step by step

Watch it work.

Open a session and see what Claude is doing right now: the command it runs, the file it reads or edits, and its latest note. When the turn ends, the answer is there, with how long it took.

Replies

Answer from anywhere.

When Claude asks for permission, the question comes to your iPhone. Allow it, deny it, or say what to do instead, and Pulse on your Mac types your answer into that session’s own terminal tab.

Allow is the Return key. Deny is Escape. A note is Escape, your words, then Return.

For Claude Code sessions in iTerm, on a Mac where Pulse is running. You can answer from the notification too.

Accounts

See how much room is left.

Each Claude account shows its five-hour session and its week, with the time until they reset. The one with the most room is marked. Tap an account and your next session starts on it.

Usage is what each account last reported through Claude Code’s status line. An account that has not reported for a week shows no data.

New sessions

Start one from the couch.

Pick an account, a folder and a model, and say what you want done. Your Mac opens a new iTerm tab, starts Claude Code in that folder and hands it your prompt.

Pulse waits until Claude Code is ready before it types. If Claude Code first asks whether you trust the folder, Pulse stops there and you confirm it on the Mac, where the tab stays open. For now this needs the shell commands its maker starts each account with, cc1 to cc4.

Pulse for Mac

At home in the menu bar.

The latest events are one click away, with each account’s usage above them. Click an event and its terminal tab comes to the front.

The two lines at the bottom say whether this Mac is registered for notifications, and what the reply channel typed last.
The whole idea

It pings.
You answer.

When a session asks for permission, or stops with a question, it reaches your phone. One tap, or a typed line, and your Mac puts the answer in the right terminal tab.

An answer you give on the phone is sent to your server, typed into the session’s terminal tab by your Mac, and marked as delivered.

Get early access
How it works

Two roads. Nothing in between.

Claude Code already tells its hooks when something happens. Pulse carries that to your pocket — and carries your answer back to the tab it came from.

A session needs you

  1. Claude Code A hook fires when a session finishes, fails or asks.
  2. The Pulse server A small server of its own — no cloud platform.
  3. Apple Push One notification per session; a new status replaces the old.
  4. iPhone and Mac On your lock screen, and in your Mac’s menu bar.

You answer

  1. You answer Allow, Deny, an option, or a line you type.
  2. The Pulse server Holds it until your Mac asks — 15 minutes, an hour for a message.
  3. The Mac app Presses the keys the prompt is waiting for.
  4. The right tab In the iTerm session that asked. Marked delivered.

Why I built it

I run several Claude Code sessions at once, across four accounts, each in its own iTerm tab. The moment one of them finished, failed or stopped at a permission prompt, it simply waited — and I only found out when I walked back to my Mac. So I built the thing I wanted: a push the second a session needs me, the steps live while it works, and a reply that lands in the right tab without me getting up.

Jarrel Pothoff

Maker of Pulse

Indie developer in the Netherlands. I build apps for iPhone and Mac, mostly with Claude Code running in the next tab.

  • Built by one person no team, no investors
  • Self-hosted by design its own small server, not a cloud platform
  • Independent not affiliated with Anthropic
FAQ

Questions, answered.

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Early access

Stop watching the terminal.
Pulse will tell you.

Pulse runs on its maker’s own iPhone and Mac today. It is not on the App Store or TestFlight yet — leave your address to hear when there is a build to try.

By joining you agree to get emails about Pulse early access and the occasional update — no spam, unsubscribe any time. See our Privacy Policy.