Skip to content

TabPulse v0.2.1

Latest

Choose a tag to compare

@github-actions github-actions released this 05 Nov 05:36
· 2 commits to main since this release
ef56b77

Install

curl -fsSL https://raw.githubusercontent.com/imtripleq/tabpulse/main/install.sh | bash

The installer downloads the latest TabPulse.zip from Releases, puts the app in ~/Applications, adds the Claude Code hooks and starts TabPulse at login.

TabPulse is ad-hoc signed and not notarized, so macOS blocks the app if you download the zip in a browser and open it yourself. To install it by hand:

  1. Unzip it and move TabPulse.app to ~/Applications.
  2. Run xattr -dr com.apple.quarantine ~/Applications/TabPulse.app.
  3. Add the hooks in Claude Code with /plugin marketplace add imtripleq/tabpulse and /plugin install tabpulse@tabpulse.

Installed this way, TabPulse doesn't start at login. See Installing the zip by hand in the README.

Changes

Fixed

  • TabPulse crashed every few hours on macOS 27 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. TabPulse now draws each spinner frame once and reuses the image.
  • A session with agents, a workflow or teammates still running in the background no longer shows as done, with a finished banner, when Claude's reply ends. It keeps working, the menu says what is still running (for example "workflow review in background"), and it finishes when a reply ends with nothing left running. Background shell commands and monitors don't count, because they are often servers or log tails that never end. If the background work sends nothing for 30 minutes, the session counts as done, so a killed task can't keep the Mac awake. This needs a Claude Code version that passes background_tasks to Stop hooks; older ones keep the old behavior.

Changed

  • The login item now runs the app itself instead of open -a, so macOS starts TabPulse again within seconds if it crashes. Quit still keeps it closed until you next log in. The installer loads the login item straight away, and the uninstaller unloads it before removing the app.