Threshold auto-fire and per-PID command delivery for every Claude Code session you run.

Why · vs. the rest · Install · Features · How it works · Roadmap

TL;DR. Lives in your tray. Watches every Claude Code session running on the box. Fires /compact, your custom Crystallize prompt, or any slash command into the exact session that needs it, before the context window crashes. Three themes. MIT.

Most usage tools tell you what already happened. Pulse acts before it happens.

• Tray-resident. Always on, never in the way. Pin to the bottom-right corner of your work area.
• Threshold auto-fire. Wire /compact (or any prompt) to the 88% mark. 10-second cancel toast. Done.
• Per-PID command delivery. Sends keystrokes to the specific Claude Code terminal that owns the session. No focus stealing, no wrong-tab accidents.
• Custom commands library. Slash commands or multi-line natural language, anything your workflow needs.
• Alert presets per session. Worker / Architect / Soul roles each have their own ceilings.
• Live everything. Tokens, model, status, 5-hour and weekly burn, Sonnet quota.
• MCP server inside. Expose live session state, usage, presets, and command library to any MCP-aware agent. Other agents can ask "where am I in my context?" and get a real answer.
• Updates itself. From v1.4.7, Pulse checks GitHub releases and installs new versions in-app. Grab it once by hand, never again.

The Claude Code tooling space is mostly read-only telemetry. Pulse is the only one that closes the loop and actually sends commands when thresholds hit.

Where Pulse loses, honestly. Windows-only today for command delivery (mac + Linux builds already compile in CI; their keystroke delivery is the v1.5 work in progress). No retrospective analytics or charts (use ccusage for that). Smaller star count: we just shipped.

Where Pulse wins. Auto-fire commands at thresholds. Per-PID precision. Custom multi-line message injection. An MCP server other agents can read from. Tray-native on Windows, the gap nobody else fills.

Windows 10 / 11

1. Grab Auralis Pulse_X.Y.Z_x64-setup.exe from Releases
2. Run it. Per-user install, no admin needed.
3. Open from Start Menu. Tray icon appears.

That's it. From v1.4.7 on, Pulse updates itself: it checks GitHub releases on launch (and every few hours) and offers to install new versions in-app, so this is the last build you grab by hand.

{
  "hooks": {
    "PermissionRequest": [
      { "hooks": [{ "type": "command", "command": "node ~/.claude/hooks/permission-forward.js" }] }
    ]
  }
}

git clone https://github.com/antonpme/auralis-pulse.git
cd auralis-pulse
npm install
npm run tauri build

Send /compact, a custom Crystallize prompt, or any slash command into the exact session you target. Works across multiple Windows Terminal tabs. Doesn't steal focus. Doesn't disturb your other Claude Code instances.

Under the hood: AttachConsole(pid) plus WriteConsoleInputW direct to the target's console input buffer, with bracketed paste mode and a two-phase write for clean multi-line submission. Falls back to SendKeys for elevated processes.

See the deep dive for the full mechanic.

Every session card shows the assigned preset (Default / Worker / Architect / Soul / your custom). Click the chip, swap the preset in a centered modal. Settings live by session_id, so a long-lived session keeps its config across Pulse restarts.

Each preset has up to three tiers (warning / pre-critical / critical), and each tier carries:

• a token threshold (absolute number or %)
• desktop notification on/off
• a command to send (or none)

When a session crosses a tier, Pulse pops a 10-second countdown toast with a Cancel button. If you don't cancel, the command fires. Hysteresis prevents oscillation re-fires after compaction.

Real example. Wire /compact to the 88% pre-critical tier on the Worker preset. When the session fills, Pulse fires it automatically. You stay in flow.

Build a library of commands once, use them across sessions. Each command carries:

• a name
• the slash command or natural language text
• single-line or multi-line (multi-line goes through clipboard paste, no SendKeys size limit)
• optional confirm prompt before sending

Compact ships seeded as a built-in.

• 5-hour window. Burn rate, % used, reset countdown.
• Weekly window. Same metrics, longer horizon.
• Sonnet quota. Tracked separately from Opus.
• All cached on disk, exponential backoff (5 → 10 → 20 → 40 → 60 min) on rate limits.
• Stale-but-cached shows on boot. Never blocks the UI.

• Color-coded fill levels. Cards shift accent as context approaches the limit. Spot the hot one without reading numbers.
• Filter by status (active / idle / ghost) or by project root.
• Sort by context %, duration, last activity, or alphabetical. State persists.
• Pin important sessions to the top with the pushpin icon. Pinned cards stay visible even when filters hide everything else.
• Ghost detection. Sessions idle for 15 min flag IDLE. Orphaned sessions (60 min low context) flag GHOST. Dismiss individually.
• Numbered cards (#1, #2, #3) so you can reference them quickly when chatting with a teammate or filing an issue.

All theming token-based: change one CSS variable, the whole UI follows.

Bottom-right of the work area. DWM-aware: handles the invisible 5-8 px shadow margin that Win11 borderless windows carry, so the visible edge actually touches the screen corner. Same code path on first build and on every tray show.

Per-session opt-in checkbox. Even if a preset fires /compact, it's blocked unless you explicitly allowed it for that session. Defense in depth for long-running agents you don't want auto-compacting on you.

From v1.4.7, Pulse updates itself. On launch and every few hours it checks GitHub releases, verifies an Ed25519 signature, and surfaces a non-silent toast: Update vX.Y.Z available with Install / Later. You choose the moment, because Pulse is watching live sessions and shouldn't restart out from under you mid-work. Install runs the NSIS installer in passive mode and relaunches. The updater's Ed25519 signature is independent of Windows code-signing, so it works without a paid certificate.

Pulse runs a Streamable HTTP MCP server on 127.0.0.1:59429. Any MCP-aware agent (Claude Code, Cursor, Continue, Zed, Claude Desktop via mcp-remote) can read live Pulse state and drive it.

Wire it into Claude Code in one command. Open Settings -> MCP inside Pulse and copy the prefilled claude mcp add command (token already inlined), or build it yourself with the URL + token from %LOCALAPPDATA%\auralis-pulse\mcp.json:

claude mcp add --transport http --scope user auralis-pulse http://127.0.0.1:59429/mcp \
  --header "Authorization: Bearer <TOKEN>"

Connect from other MCP clients. Same server, different config files. Grab the token from Pulse's Settings -> MCP tab (Reveal + Copy) or from %LOCALAPPDATA%\auralis-pulse\mcp.json, then paste it into the snippet for your client.

{
  "mcpServers": {
    "auralis-pulse": {
      "url": "http://127.0.0.1:59429/mcp",
      "headers": {
        "Authorization": "Bearer <TOKEN>"
      }
    }
  }
}

mcpServers:
  - name: auralis-pulse
    type: streamable-http
    url: http://127.0.0.1:59429/mcp
    requestOptions:
      headers:
        Authorization: Bearer <TOKEN>

{
  "context_servers": {
    "auralis-pulse": {
      "url": "http://127.0.0.1:59429/mcp",
      "headers": {
        "Authorization": "Bearer <TOKEN>"
      }
    }
  }
}

{
  "mcpServers": {
    "auralis-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:59429/mcp",
        "--transport",
        "http-only",
        "--allow-http",
        "--header",
        "Authorization:Bearer ${AURALIS_PULSE_TOKEN}"
      ],
      "env": {
        "AURALIS_PULSE_TOKEN": "<TOKEN>"
      }
    }
  }
}

Quick sanity check. Once wired, ask the client to call pulse_ping. The expected response is "pong (auralis-pulse vX.Y.Z)", where the version matches your installed Pulse. If the version string comes back, MCP transport and bearer auth are both healthy.

Tools available today (v1.4.7, ten total):

Read:

Write:

Bearer-token auth, localhost-only by design. The MCP tab inside Settings (v1.4.3) shows port, masked token, and a copy-button for the full claude mcp add command. Server-pushed notifications (threshold-crossed, session-added, session-removed, usage-updated) landed in v1.4.4 so connected clients react instantly without polling. Per-client setup snippets (v1.4.5) for Cursor, Continue, Zed, and Claude Desktop via mcp-remote are in the collapsible blocks above.

Three subsystems.

Renderer. Reads ~/.claude/sessions/ and JSONL transcripts from ~/.claude/projects/. Refreshes locally every 30 seconds, free, no API calls. Process-name verification prevents PID-reuse false positives when sessions die and Windows recycles their PIDs.

Per-PID command delivery. Bypasses focus and targets the right terminal even when you have multiple Claude Code tabs in Windows Terminal. Deep-dive below.

Anthropic API. OAuth usage call every 5 minutes. Disk cache at %LOCALAPPDATA%\auralis-pulse\usage-cache.json. Exponential backoff on 429.

• v1.3 Custom commands, alert presets, per-PID delivery, auto-compact safety, pin sessions, DWM-aware window pinning, preset chip, modal picker, DOM split for overlay isolation. v1.3.6 bugfix: Anthropic usage API resilience (nullable resets_at, refresh error toast, clear-cache button)
• v1.4 ongoing through v1.4.8:
  • v1.4.0 Autostart preference persistence + diagnostic file logger (pulse.log) + MCP server foundation (Phase 1)
  • v1.4.1 MCP Phase 2: five read tools (pulse_list_sessions, pulse_get_session, pulse_get_usage, pulse_list_presets, pulse_list_commands) + JS↔Rust state mirror
  • v1.4.2 MCP Phase 3: four write tools — pulse_send_command(pid, text) injects a slash command or natural-language message into a specific Claude Code session, pulse_assign_preset(session_id, preset_id) swaps a session's alert ceiling (round-trips through the frontend so localStorage stays consistent), pulse_refresh_usage forces an Anthropic OAuth fetch, pulse_clear_usage_cache nukes the disk cache. Closes the loop: agents can now act on Pulse, not just read from it.
  • v1.4.3 MCP Phase 5: new MCP tab inside Settings — shows port, URL, masked token (with Reveal/Hide), one-click copy for the bearer token and the full claude mcp add command, plus a summary of exposed tools. No more digging through mcp.json to wire a client.
  • v1.4.4 MCP Phase 4: server-pushed notifications over the MCP notifications/message channel. Pulse broadcasts four event kinds with structured { kind, payload } data: threshold-crossed (per-preset, fired by the frontend hysteresis loop, carries session_id/pid/tier/used_tokens/limit_tokens/preset_name), session-added and session-removed (diffed every 30s in the backend session refresh loop), usage-updated (after every successful Anthropic OAuth fetch, slim payload with five_hour_pct/weekly_pct/sonnet_pct). Server-side Peer<RoleServer> capture in on_initialized, transport-closed peers dropped on every broadcast. Connected clients get instant reactions, no polling.
  • v1.4.5 MCP Phase 6: per-client setup docs. Copy-paste config snippets for Cursor (.cursor/mcp.json), Continue (config.yaml), Zed (settings.json), Claude Desktop (via mcp-remote bridge), plus a single pulse_ping sanity check shared across all four. Documentation-only; no runtime changes.
  • v1.4.6 MCP tab UI cleanup: bearer token in the Quick Start command now masks until Reveal (Copy still emits the real token), command wraps without breaking Bearer mid-word, em-dash removed from the verify hint, and the Exposed Tools list stacks cleanly instead of colliding with its label.
  • v1.4.7 Auto-update: Pulse checks GitHub releases on boot and every 6h, verifies an Ed25519 signature, and offers a non-silent Update vX.Y.Z available [Install] [Later] toast. Install runs the NSIS installer in passive mode and relaunches. No more manual reinstall on every patch (this is the last version you install by hand).
  • v1.4.8 Fable 5 model detection: recognises the new claude-fable-5 (was showing a raw name + 200K), maps it to its confirmed 1M window, and surfaces a [1m] marker in the label. Context window is now driven by the [1m] marker rather than hardcoded per family. Plus 8 unit tests for the model parser. First version delivered via auto-update.
• v1.5 Cross-platform (in progress):
  • GitHub Actions CI matrix compiles macOS (.dmg, Apple Silicon + Intel), Linux (.deb / .AppImage), and Windows. All builds green; the Rust code already gates Windows APIs behind cfg(windows).
  • macOS command delivery via iTerm2 Python API (currently a "Windows only" stub)
  • Linux command delivery via tmux send-keys
  • Signed cross-platform releases through tauri-action (mac/linux auto-update)
• Future Configurable keyboard shortcuts, session activity timeline, command chains (Crystallize, then wait, then Compact), Discord callback integration, Tailscale plus PWA for remote mobile access, plugin system

Full plan: ROADMAP.md

Issues and PRs welcome. Pulse started as a personal tool and grew. If you use Claude Code heavily on Windows, the per-PID delivery and threshold auto-fire might be worth keeping around.

MIT © 2026