Skip to contentSkip to contact
Dennis KhorTabPulse
Recruiter mode

ProductmacOSSince November 2026MIT licence

TabPulse

Four sessions, one night, every moon in view.

See which Claude Code sessions are working, waiting on you or done, right on your Ghostty tabs and in your macOS menu bar.

Moon spinnereight frames, new moon to waning crescent,a frame every 0.12 s

  • Hook events9from SessionStart to SessionEnd
  • Spinner tick0.12 severy working tab steps together
  • Network calls0everything stays on your Mac

01 The problem

Only the tab you're looking at moves.

Claude Code only animates the tab you're looking at, so from any other tab a busy session looks idle. Click another tab in the window: the motion follows you, not the work.

The Ghostty window, menu bar, tab names and times on this page are drawings, not screenshots.

02 What you get

Every working tab gets a moon.

You start four sessions and look away. TabPulse puts a spinner on every working Ghostty tab, and they all step together, one frame every 0.12 seconds. The ✳︎ in the menu bar counts the sessions that are working.

This page uses Moon, one of 16 tab spinners and the style in the README demo. The default is Braille.

One needs an answer.

Claude stopped to ask for permission to use Edit. That tab's moon becomes ●, the menu bar gets an orange dot, and ⌃⌥⌘J jumps to the tab that needs you from any app.

If it waits five minutes, you get one reminder, once per wait.

Another one finishes.

Its moon goes out and Claude's own title comes back. About ten seconds later a Finished banner arrives, unless you're already looking at that tab, and a green dot waits in the menu bar until you've seen it.

The moons rise into the menu bar.

The whole night ends up in one place: how many sessions are working, an orange dot when one needs you, and a green dot when one finished while you were elsewhere. With more sessions working, the ✳︎ spins faster.

Click it for the list.

Each session shows what it's doing and for how long, with the one that needs you at the top. Click a row to jump to its Ghostty tab. While Claude works, TabPulse keeps your Mac awake, and the screen can still sleep.

03 How it works

Hooks in, titles out.

A small hook script writes each session's state to a JSON file. It prints nothing and always exits 0, so it can't block or change a session. TabPulse reads those files once a second, updates the menu bar and sets the Ghostty tab titles.

The path, in order: Claude Code fires a hook event, tabpulse-hook.sh writes the session file, TabPulse.app reads the files and sets the Ghostty tab titles and the menu bar.

Send one session through a turn

  1. A new session is written as done. Nothing is working yet, so TabPulse leaves its tab alone.

  2. You send a prompt. The session is working, and its tab gets a spinner.

  3. Claude runs a tool, and the menu row says which one. An MCP tool shows its short name, so mcp__github__create_issue reads as create_issue.

  4. Claude needs your permission to use Edit. The spinner becomes ● and the menu bar gets an orange dot.

  5. You answered and the tool ran. The turn clock kept running through the prompt, so the row still says how long the whole turn has taken.

  6. The reply ended, but a workflow is still running in the background, so the session keeps working. This needs a Claude Code version that passes background_tasks to Stop hooks.

  7. The turn is over. TabPulse hands the title back to Claude, and about ten seconds later a Finished banner arrives, unless you are on that tab.

  8. The session ends. The hook deletes its file, and the row leaves the menu.

You send a prompt. The session is working, and its tab gets a spinner.

The hook writes sessions/<id>.json

{
  "state": "working",
  "detail": "thinking",
  "event": "UserPromptSubmit",
  "background": "",
  "cwd": "/code/api-tests",
  "tty": "/dev/ttys004"
}
plus since, turn, updated and pid

The tab shows

api tests

The menu row says

🌓api testsworking, thinking0:01

TabPulse asks Ghostty

set name override of (first terminal whose tty is "/dev/ttys004") to "🌓 api tests"

Titles it owns, and gives back

TabPulse puts its mark in front of Claude's own title and hands the title back when the turn ends. Every ten seconds it peeks at Claude's title, to keep it current and to spot a turn stopped with Esc.

Only notices that wait on you

A session counts as needing you for permission prompts and dialogs, not for every notification. Compaction leaves the state alone, and an API error ends the turn as Stopped.

No more access than it needs

TabPulse never launches Ghostty or asks for Automation access just to look for a tab, and ⌃⌥⌘J needs no Accessibility permission. Under Reduce Motion each tab holds one frame; Moon holds 🌓.

04 Built to ship

Each change to the app runs the same checks.

CI builds and tests every pull request and every push to main. A release goes out only after the whole of CI passes and the tag matches VERSION.

  • Swift
  • AppKit
  • AppleScript
  • bash
  • jq
  • GitHub Actions

CI on pull requests and pushes to main

  1. Build universal appscripts/build.sh --universal, arm64 and x86_64
  2. Smoke testthe built app, before the checks
  3. Hook testsscripts/test-hook.sh
  4. Logic testsscripts/test-logic.sh
  5. Installer testsscripts/test-install.sh
  6. Shellcheckinstaller, uninstaller, scripts and the hook
  7. Versions agreeVERSION, plugin.json, marketplace.json
  8. Plugin hook events match the installer'shooks.json against install.sh EVENTS

Release on a version tag

  1. CIthe whole CI workflow runs first
  2. Tag matches VERSIONthe tag against the VERSION file
  3. Build universal appscripts/build.sh --universal
  4. PackageTabPulse.zip and its checksum
  5. Release notes from CHANGELOG.mdthe section for this version
  6. Publisha GitHub release with the notes

What CI and a release run, step by step. Each moon fills as its step runs.

Tests that need no XCTest

test-hook.sh feeds fake hook events to the hook and checks the file it writes. test-logic.sh builds the app's pure decision logic into a small command line tool. test-install.sh runs both scripts against a throwaway HOME.

An installer that checks first

It verifies the zip against its published SHA-256 and stops if that file is missing or doesn't match. It edits only the hooks in settings.json, keeps a backup, and checks the JSON is valid before it changes anything.

An uninstaller that goes in order

It removes the hooks from settings.json before deleting anything else, and stops with nothing removed if it can't, so no hook is left calling a missing script.

A crash, fixed at the source

On macOS 27 it crashed every few hours while its menu was open, inside Apple's text drawing, which ran 8 times a second for the spinners. Now each spinner frame is drawn once and reused, and macOS restarts the app within seconds if it ever crashes.

Builds with the Command Line Tools

build.sh calls swiftc directly instead of SwiftPM, so building from source needs only the Xcode Command Line Tools.

Requirements and licence

macOS 14 or newer, Claude Code 2.1.78 or newer, and Ghostty 1.4 or newer for the tab spinners. The menu bar works with any terminal. MIT licensed.

Product3 Nov 2026 to now

TabPulse

An open source macOS menu bar app and Claude Code plugin that puts a live spinner, such as moon phases, on every working Ghostty tab and a dot on any tab that needs you.

Built with an AI pair programmer, then reviewed and tested by me. The tests and decision records below are how I hold that work to account.

Kind
Product
Platforms
macOS
Period
3 Nov 2026 to now
Stack
  • Swift
  • AppKit
  • IOKit
  • AppleScript
  • Bash
  • launchd
  • Claude Code hooks
  • GitHub Actions
  • GitHub Pages
  • Hook events9
  • Styles16tab spinners, 24 menu bar
  • Network requests0

The problem

Claude Code only animates the tab you're looking at, so from any other tab a busy session looks idle. With four sessions open in four Ghostty tabs, the only way to know which one is working, which one is waiting for a permission and which one finished was to click through them all.

TabPulse is an open source macOS menu bar app and Claude Code hook that fixes that. It puts a spinner on every working Ghostty tab, a dot on any tab that needs you, and a count of working sessions in the menu bar, with an orange dot when one needs you and a green dot when one finished while you were elsewhere. It shipped on 3 Nov 2026 under the MIT licence.

Constraints

  • The hook runs inside every Claude Code session, on 9 hook events. Nothing it does may block a session, slow it down or change what Claude sees.
  • No network calls. A status app that watches every coding session sees the titles and progress of private work, so everything stays on the Mac.
  • macOS 14 or newer, Claude Code 2.1.78 or newer, and Ghostty 1.4 or newer for the tab spinners. The menu bar works with any terminal, but the spinners need Claude running directly in a Ghostty tab, not inside tmux, screen or zellij.
  • Building from source needs only the Xcode Command Line Tools: no Xcode project, no XCTest, no SwiftPM at build time.
  • The builds are signed ad hoc and not notarized, so the installer has to earn trust another way.
  • It respects Reduce Motion.

What I built

Two pieces talk through files. tabpulse-hook.sh, in bash and jq, runs on SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PostToolUseFailure, Notification, Stop, StopFailure and SessionEnd. It writes one JSON file per session to .claude/tabpulse/sessions/ in the user's home folder, with the state (working, waiting or done), when the state and the turn began, and what the session is doing, such as running Bash or permission to use Edit. The installer and a Claude Code plugin share the same script.

The TabPulse app, in Swift and AppKit, reads those files once a second. It sets each Ghostty tab title through AppleScript's per-terminal name override, draws the menu bar pill and the session list, and jumps to a session's tab when you click its row. A Finished banner arrives about ten seconds after a turn ends, unless you're already looking at that tab. A reminder comes once a session has waited on you for 5 minutes, and Control-Option-Command-J jumps to the tab that needs you from any app. While Claude works, it holds a power assertion so the Mac stays awake and the screen can still sleep.

There are 16 tab spinners and 24 menu bar animations. Each spinner frame shows for one 0.12 s tick, and every working tab steps on the same tick. Under Reduce Motion every tab spinner but Garden holds one frame, and the menu bar shows a still pose. A one-line installer, an uninstaller and a website on GitHub Pages complete it.

I built TabPulse with an AI pair programmer; every change went through the checks below and my review.

Decisions that mattered

A hook that cannot hurt a session

The hook never prints to stdout and always exits 0, so it can't inject text into a Claude session or block one. All it can ever do is write its file. It refuses session ids that contain / or start with ., since the id becomes a file name, and it does nothing at all without jq.

Files and Ghostty only

The app reads the session files, sends AppleScript only to Ghostty and makes no network requests. It never launches Ghostty or asks for Automation access just to look for a tab: it checks Ghostty is running and has access before any other call. Even the fallback banner, sent through osascript when macOS refuses TabPulse's own notifications, passes the title and text as arguments, never as script, so a tab title can't change what runs.

Titles it owns, and gives back

TabPulse puts its mark in front of Claude's own title and hands the title back with an empty override when the turn ends. It records every terminal whose title it changed, so it can hand them back after a crash. Every ten seconds it peeks at Claude's own title, to keep it current and to spot a turn stopped with Esc.

An installer that checks before it edits

The one-line installer edits the same settings.json that holds a user's other hooks. It checks the file is valid JSON before it downloads anything, backs it up, verifies the release zip against the SHA-256 file published with it and changes only the hooks section. The uninstaller removes the hooks before deleting anything else, and stops with nothing removed if it can't, so no hook is left calling a missing script.

One narrow sudoers rule for lid-closed mode

Keeping a Mac awake with the lid closed needs pmset as root. The opt-in lid-closed mode asks for an admin password once and installs a rule that lets only that user run only pmset -a disablesleep 1 and 0, checked by visudo first. Lid sleep is off only while Claude works, and comes back on when the work ends, the battery drops to 20% or the Mac gets hot.

Hard problems

A crash inside Apple's text drawing

On macOS 27, TabPulse crashed every few hours while its menu was open. The exception came from inside Apple's text drawing code as it drew a session's spinner, which happened 8 times a second. The fix was to stop asking for that text on every frame: each spinner frame is now drawn once and the image reused. The same release changed the login item to run the app directly, so launchd starts it again within seconds if it ever exits with an error, where before a crash left it off until the next login.

Knowing when a turn is really over

A Stop event looked like the end of a turn, but a reply can end while agents, a workflow or teammates keep running in the background, and TabPulse then showed the session as done with a Finished banner. The hook now keeps such a session working and the menu says what is still running, for example "workflow review in background". Background shell commands and monitors don't count, because they are often servers or log tails that never end, and 30 minutes of silence counts as done, so a killed task can't keep the Mac awake. The banner waits about ten seconds so a Stop hook that sends Claude back to work can cancel it.

How it is tested

There is no XCTest. Three scripts cover the behaviour instead:

  • test-hook.sh feeds fake hook events to the hook and checks the file it writes.
  • test-logic.sh builds the app's pure decision logic, the keep-awake policy, the reminder and where Control-Option-Command-J goes, together with Tests/LogicTests.swift into a small command line tool and runs it.
  • test-install.sh installs and uninstalls into a throwaway HOME with a stand-in sudo that only logs, so it never touches a real .claude folder, the running app or a sudoers rule.

CI builds a universal app for arm64 and x86_64, runs a smoke test, the three scripts and shellcheck on every pull request and push to main. It also checks that the plugin's hook events match the installer's and that the versions agree. A tag push runs the whole of CI first, and only then does the release check the tag against VERSION, build the app and publish TabPulse.zip with its checksum.

Results

TabPulse is public on GitHub with a website on GitHub Pages. It went from its first release to its third in three days, and the third fixed what real use found: the background work that ended turns too early, and the crash on macOS 27. The tab spinners, the menu and the banners all work from 9 hook events and one file per session, with no network calls.

What I would do next

  • Tab spinners for other terminals: iTerm2, WezTerm, kitty and Apple's Terminal. Each needs the same five calls Ghostty answers over AppleScript, set a title by tty, read one, list them, focus a tab and say which tab is in front.
  • Notarized builds, so macOS stops asking for permission again after every update, and a Homebrew cask.

Milestones

What shipped, and when.

  1. First release, open source: a spinner on every working Claude Code tab

  2. Keeps the Mac awake while Claude works, with reminders and a jump shortcut

  3. A menu crash on macOS 27 fixed by drawing each spinner frame once

  4. Website live on GitHub Pages

Decisions

6 decision records shown here. Open one to read its context and consequence.

  1. Accepted

    The hook never prints and always exits 0

    The hook writes one small file per session, never prints to stdout and always exits 0.
    Context
    Claude Code runs TabPulse's hook on nine events in every session, so a fault in the hook could reach the session itself.
    Consequence
    It cannot inject text into a Claude session or block one, and the app reads every status from those files.
  2. Accepted

    Local files and Ghostty only, no network

    The app reads the session files once a second, sends AppleScript only to Ghostty and makes no network requests.
    Context
    A status app that watches every coding session sees the title and progress of private work.
    Consequence
    Nothing about a session leaves the Mac, and TabPulse never launches Ghostty or asks for Automation access just to look for a tab.
  3. Accepted

    The installer checks and backs up before it edits

    It verifies the release zip against its published SHA-256 file, checks settings.json is valid JSON, backs it up and changes only its hooks section.
    Context
    The one-line installer edits the same settings.json that holds a user's other Claude Code hooks.
    Consequence
    A corrupt or incomplete download stops the install, and the uninstaller removes the hooks before it deletes anything else.
  4. Accepted

    Lid-closed mode gets one narrow sudoers rule

    An opt-in mode installs one rule that lets only the user run only pmset -a disablesleep 1 and 0, checked by visudo and installed 0440 root:wheel.
    Context
    Keeping a Mac awake with its lid closed needs pmset as root, and a password prompt every time would defeat the point.
    Consequence
    Lid sleep is off only while Claude works, and it comes back on when the work ends, the battery runs low or the Mac gets hot.
  5. Accepted

    Draw each spinner frame once

    Draw each spinner frame once and reuse the image, instead of drawing the text on every frame.
    Context
    TabPulse crashed every few hours on macOS 27 while its menu was open, inside Apple's text drawing code, which drew each spinner 8 times a second.
    Consequence
    The menu no longer calls into the text drawing code that crashed it on every frame.
  6. Accepted

    launchd restarts the app after a crash

    The login item runs the app directly, and launchd starts it again only when it exits with an error.
    Context
    With open -a as the login item, a crash left TabPulse off until the next login.
    Consequence
    macOS starts TabPulse again within seconds of a crash, and Quit still keeps it closed until the next login.

Live status

Sampled 16 Nov 2026, 02:51 UTC. Failures are shown as they were read.

Ask about fit

Paste a job description. You get a verdict, the evidence that matches it with citations, and what the sources do not show.

Open to senior AI and software engineering roles: on site or hybrid in Sydney, or remote for Australian and US teams.

Email meBook 15 minCV