Does SpectiX send my code or session data anywhere?

No. SpectiX runs entirely on your Mac and the binary opens no connection at all. It reads local process state and local status files under ~/.claude/spectix/. You can confirm this from outside the app by running it behind an outbound firewall such as Little Snitch: the only connections it ever makes follow a press of yours in the account panel — its refresh button, or a click on another Claude account to switch to it — each of which asks Anthropic's own usage endpoint for that account's quota and sends nothing else.

SpectiX is closed source — how can I verify it makes no network calls?

Without reading any source, using four checks against the copy you downloaded. 1) codesign -d --entitlements - /Applications/SpectiX.app lists exactly one entitlement, com.apple.security.automation.apple-events, and no network entitlement; that list lives inside the code signature, so altering the app breaks it. 2) otool -L on the binary shows no CFNetwork, no Network.framework, no libcurl and no libssl — the machinery to make requests is absent. 3) lsof -i -a -p $(pgrep -x SpectiX) prints nothing while it runs; an outbound firewall such as Little Snitch or LuLu never prompts, and the app works identically with Wi-Fi off. 4) spctl -a -vvv reports source=Notarized Developer ID, so Apple scanned this exact build and macOS can prove the copy on disk is the one that was signed.

macOS asks me to confirm when I first open SpectiX. Is that normal?

Yes. SpectiX is signed with an Apple Developer ID and notarized by Apple, so macOS shows the standard one-time confirmation for any app downloaded from the web. Click Open. You will not see the 'unidentified developer' warning, and the prompt does not appear again.

What are SpectiX's system requirements?

macOS 13.0 or later, on Apple Silicon or Intel. Pane-level jumping inside VS Code additionally uses a companion editor extension, which the installer sets up.

What happens to a SpectiX build on 31 March 2027?

This build works through 31 March 2027 and then stops. It does not keep running in a reduced form: it shows where to download a current build and nothing else, so session monitoring, jumping, shortcuts and sounds all stop until a current build is installed. SpectiX has no update check; the date is how it tells you a newer build exists, and the app says so from inside itself for the last seven days. The date is the same in every copy of a given build. Nothing you configured is erased — install the current build and every setting, theme and project icon comes back as you left it, free, with nothing to buy and nothing to sign up for.

Your agents run in parallel.
Your attention doesn't.

Q: Why does SpectiX need Accessibility permission?

SpectiX uses Accessibility access for two things only: reading window and tab titles so it can match a session to its terminal, and raising and focusing that window (including the correct split pane) when you click a row. It never reads terminal contents, code, or Claude transcripts, never takes screenshots, and opens no connection you did not ask for. It does not request Screen Recording.

Q: How does SpectiX know a Claude Code session's status?

It fuses three independent sources: the Claude Code hooks write a state file per terminal, the app inspects that terminal's process tree to see whether work is actually running, and the daemon's session state fills in cases the hooks cannot reach, such as a background subagent asking for permission. Everything is keyed by controlling tty, which is unique per terminal and stable for its whole life.

Q: How do I remove SpectiX completely?

Drag SpectiX.app to the Trash (or use the installer's uninstall option, which does all of this), delete ~/.claude/spectix and remove the spectix-status.sh hook entries from ~/.claude/settings.json, then revoke the permission in System Settings > Privacy & Security > Accessibility.

Every Claude Code session in your menu bar — which one finished, which one is blocking on you, and one click back to its terminal.

Download for macOS What it can and cannot see

macOS 13.0 or later · Apple Silicon & Intel · Signed & notarized by Apple · No connection you did not ask for

SESSIONS1 needs you

auth-flow

VS Code · ttys004 · waiting on your approval

Needs you

api-refactor

▸ Edit · router.ts

Working

fix-flaky-tests

⏱ 6m 12s · 84k tokens · ✦ Sonnet 5

Done

docs-pass

Terminal · ttys009

Idle

Every session you are running, ranked so the one blocking you is on top.

Runs entirely on your Mac· No connection you did not ask for· Signed & notarized by Apple· Not affiliated with Anthropic

It reads process state and the status files the hooks write — not your transcripts.

Why it exists

Built to give you four things back.

SpectiX has one job: keep the cost of running AI agents from landing on you. Every feature is measured against these four promises.

Your time

No more patrolling terminals to find out who finished. One glance at the menu bar tells you whether anything needs you, and one click puts you there — cursor already in the input box.

Your attention

Working sessions stay silent. You are interrupted only when a session is actually blocking on you, most urgent first, and the alert clears itself the moment you look.

More out of every AI you run

Run five sessions with the same confidence as one. See what each is doing right now, how long it has been at it, and how much of its context and your subscription quota is left — so you feed the next task at the right moment instead of guessing.

Your health

Staring at a spinner is not work. When nothing needs you, SpectiX stays out of the way — get up, stretch, look away from the screen. The session that needs you will come and find you.

What it does

Four things, done properly.

One click back to the exact terminal — even the third pane in the same VS Code window

Click a row and you land in that session's terminal with the cursor in its input box, and a breathing ring lights up the pane you landed on. Pane-level, not window-level. ⌃⌥⌘N walks you to the next session that needs you.

A VS Code window with three integrated terminal panes open along the bottom. The middle pane is outlined by a bright red breathing ring marking the session just jumped to, and two SpectiX alerts sit stacked in the top-right corner of the screen. — **The landing ring.** Three terminals in one window, and no doubt about which one you were just sent to. Eight ring styles, configurable per status.

Status you can trust

SpectiX does not decide a session's state from one signal. It fuses the Claude Code hook events, live inspection of the process tree, and the daemon's own session state. That is why it does not stay red after you click approve, and why it keys everything by tty — the one identifier that stays put for the life of a terminal.

The SpectiX main window on its Sessions tab: sessions grouped under the project window they belong to, each group header carrying a count per status, and each row showing elapsed time, tokens used and the model it is running on. — **The main window.** Grouped by project window, with per-status counts on the header.

Status and usage in one place

A working row shows the tool step it is on right now (▸ Edit · router.ts). A finished row shows elapsed time, tokens, the model that session is on, and how much of its context window is gone — so you know who is burning Opus on chores before you open anything.

The SpectiX main window on its Stats tab: an impact score, hours of waiting saved, a streak counter, the number of jumps taken, and totals for sessions, active time and estimated cost. — **The Stats tab.** How much waiting it saved you, how many jumps it took for you, and what the week cost.

Two accounts, one CLI — switch without signing in again

Claude Code and Codex each hold one sign-in at a time, so a second account otherwise means logging out and back in. Click the account card in the header and every address you have used is listed with its plan and how much of its five-hour and weekly limit is gone. Pick one and the next terminal you open is on it — sessions already running finish on the account they started.

The Claude account panel open below the header: three remembered addresses, each with its plan badge and two quota bars showing how much of the five-hour and weekly limit is used and when each resets. A tick marks the account currently signed in. — **The account panel.** Claude and Codex keep separate lists, each address with the quota it has left. The switch applies to newly opened terminals.

The Codex account panel open the same way, with two remembered addresses, their plan badges and the same pair of quota bars. — **The account panel.** Claude and Codex keep separate lists, each address with the quota it has left. The switch applies to newly opened terminals.

The question you were about to ask

Why does it need Accessibility access?

Because jumping you back to the right terminal means touching other apps. That is macOS's definition of an "accessibility" action, and macOS is right to gate it. Here is exactly what SpectiX does with the permission — and what it never does.

What it does with the permission

Reads window and tab titles, so it can find the terminal that belongs to a session
Raises that window and focuses the correct split pane when you click a row
Draws the highlight ring on the pane it landed on

What it never does

Read the contents of your terminal, your code, or your Claude transcripts
Take screenshots or record your screen — Screen Recording is not requested at all
Send your sessions, code or transcripts anywhere. Nothing goes out unless you press something that says it will — in the account panel, its refresh button and a click on another Claude account to switch to it each ask for that account's quota, and carry nothing else.
Keep running in the background once you quit it

SpectiX is closed source — so don't take any of that on faith. Reading source wouldn't settle it anyway: the thing running on your Mac is the binary, not the source. So every claim above is written to be checked against the copy you downloaded, from outside it. Three commands, and none of them need anything from us:

It asked for one permission, and it isn't network. The entitlement list lives inside the code signature — change one byte of the app and the signature breaks and macOS won't launch it.
codesign -d --entitlements - /Applications/SpectiX.app → com.apple.security.automation.apple-events — that's the whole list → no network.client, no network.server, nothing else
The binary has no network stack in it. An app can't make requests without the machinery to make them, and it verifiably isn't there.
otool -L /Applications/SpectiX.app/Contents/MacOS/SpectiX → Cocoa, AppKit, Foundation, Carbon, CoreGraphics, Swift runtime → no CFNetwork, no Network.framework, no libcurl, no libssl
Zero sockets while it runs. Not "a few harmless ones" — none, on launch and after a week of uptime.
lsof -i -a -p $(pgrep -x SpectiX) → no output at all
Stronger versions of the same check: leave it behind Little Snitch or LuLu for a week — it will never once ask you to allow a connection, with two exceptions you have to press yourself, both in the account panel: its refresh button, and a click on another Claude account to switch to it — each starts curl to fetch that account's quota, and that is the connection a firewall will ask about. Or just turn off Wi-Fi and use it all day: every feature behaves identically, because none of them ever involved the network — the two presses that do use it fail quietly, and the row keeps its last figure.
It's the copy we signed, and Apple scanned it. Signed with an Apple Developer ID and notarized, so macOS can prove the app on your disk is byte-for-byte the one that was signed (spctl -a -vvv /Applications/SpectiX.app → source=Notarized Developer ID).

And the screen claim needs no command at all: macOS won't let any app read your screen without listing it under System Settings › Privacy & Security › Screen Recording. SpectiX isn't there, and never asks to be. Full detail, permission by permission, on the privacy page.

Before you install

Where it works

Two questions, two different answers: whether a session shows up at all, and whether clicking its row sends you back to it. The first works everywhere. The second needs a host SpectiX knows how to drive, so here is the list.

Seeing a session — any host

Claude Code running in any terminal, editor, SSH session or tmux window appears in the list.
Status accuracy does not depend on the host — everything is keyed by the session's controlling tty.
One boundary, and it is ours: a host that never allocates a pty produces no row at all rather than a wrong one. The full write-up is here.

Click-to-jump and the ring — these hosts today

Terminals: Terminal.app · iTerm2
Editors: VS Code · Cursor · Windsurf — down to the right terminal pane inside a window, with the breathing ring on the pane you landed on
Desktop app: Claude for Desktop, detected through Accessibility

Planned — hosts we intend to add jump support for

Terminals: Ghostty · WezTerm · kitty · Alacritty · Warp · Hyper · Tabby
Editors: Zed · JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, GoLand, RustRover…) · Xcode
Session shapes: tmux panes and ssh sessions — landing on the pane itself rather than the window that happens to contain it
No dates, and none of this is a commitment to a particular release. The order follows what people actually run, so telling us which host you use is what moves it up.

Until then those rows still work — the click just doesn't jump. Every host on the planned list is already shown with the same status accuracy as any other session; it simply is not a jump target yet, and no ring is drawn for it. Supported hosts are an explicit allowlist rather than a guess — which is why the list can be written down at all, instead of "most terminals".

Claude Code today. Sessions belonging to Codex, Gemini CLI or Aider are not tracked yet — they are on the roadmap.

No surprises

Install in 30 seconds

STEP 1

Download the installer

One file, one icon. Nothing to configure first.

STEP 2

Open it and click Install

It puts SpectiX in Applications, installs the status hooks into ~/.claude, and adds the companion editor extension if you have VS Code, Cursor or Windsurf. Nothing else on your system is touched.

STEP 3

macOS asks you to confirm — once

That is the standard prompt every app downloaded from the web gets. Click Open. It does not come back.

SpectiX is signed with an Apple Developer ID and notarized by Apple, so you will not see the "unidentified developer" warning, and you will never be asked to strip a quarantine flag from the terminal or dig through System Settings to allow it. If any Mac app asks you to do that, it has not been notarized.

Stop patrolling terminals. Let them tell you.

Free. Runs on macOS 13.0 and later, Apple Silicon and Intel, and never phones home.

Download for macOS What it touches on your Mac

Signed & notarized by Apple · No connection you did not ask for · Uninstalls cleanly (how)

What's next

Still being built.

New builds and fixes land on this page. Here is what is being worked on next — no dates attached, and the order follows what people actually run.

More terminals and editors

Ghostty, WezTerm, kitty, Zed, the JetBrains IDEs and Xcode — each with click-to-jump and the ring, down to the right pane. What already works is listed above.

Beyond Claude Code

Codex, Gemini CLI and Aider in the same panel — every agent you have running in one place, instead of one menu bar item per tool.

tmux and ssh, down to the pane

Those sessions already appear with full status accuracy. What is missing is landing on the pane itself rather than the window that happens to contain it.

No dates, and none of this is a commitment to a particular release. What moves an item up the list is someone saying they need it — so if the host or the agent you use is on it, say so. Everything that has shipped so far is in the changelog, which is also the honest way to check whether this thing is still alive.

Questions

Frequently asked

Why does SpectiX need Accessibility permission?

For two things only: reading window and tab titles so it can match a session to its terminal, and raising and focusing that window — including the correct split pane — when you click a row. It never reads terminal contents, your code, or your Claude transcripts, never takes screenshots, and opens no connection you did not ask for. It does not request Screen Recording at all.

Does it send my code or session data anywhere?

No. SpectiX runs entirely on your Mac and the binary opens no connection at all. It reads local process state and the local status files under ~/.claude/spectix/.

You can verify that from outside the app: run it behind an outbound firewall such as Little Snitch and nothing will ever ask for permission — with two exceptions you have to press yourself, both in the account panel: its refresh button, and a click on another Claude account to switch to it. Each asks Anthropic's own usage endpoint for that account's quota, using that account's access token and sending nothing else. It happens on those presses and at no other moment: not when the panel opens, never on a timer.

It's closed source — why should I trust it?

You shouldn't have to. Publishing the code wouldn't actually settle this question either: what runs on your Mac is the binary, not the source, and nothing ties one to the other unless you compile it yourself.

So SpectiX is built to be audited from outside instead — against the exact copy you downloaded. Its signed entitlement list contains one permission and no network one (codesign -d --entitlements -). Its binary links no network stack at all (otool -L). It opens no sockets while running (lsof -i -a -p $(pgrep -x SpectiX) prints nothing). And Apple has notarized this exact build (spctl -a -vvv). Four checks, none of which rely on our word — the full walkthrough with expected output is on the privacy page.

How does it know a session's status?

Three independent sources, resolved in priority order: the Claude Code hooks write a state file per terminal; the app inspects the process tree of that terminal to see whether work is actually running; and the daemon's session state fills in cases the hooks cannot reach, such as a background subagent asking for permission.

Everything is keyed by controlling tty, which is unique per terminal and stable for its whole life — unlike session IDs, which can change inside a single process, or the SSE port, which every terminal in one VS Code window shares.

Is SpectiX affiliated with Anthropic?

No. SpectiX is an independent, unofficial tool and is not affiliated with, endorsed by, or sponsored by Anthropic. Claude and Claude Code are trademarks of Anthropic, PBC.

How do the hooks get installed?

The installer writes ~/.claude/hooks/spectix-status.sh and registers the hook entries in ~/.claude/settings.json for you. If you already have hooks configured, yours are preserved. Hooks only affect sessions opened after installation, or sessions that are still active — a terminal that has fired no event since install has no state file yet.

Which Claude Code versions are supported?

SpectiX uses the documented Claude Code hook events and the local session state the CLI already maintains, so it tracks current releases. The exact verified version range is published with each release on the changelog.

macOS says it cannot open the app — what do I do?

On first launch macOS shows a one-time confirmation for anything downloaded from the web: click Open. That is the normal dialog, not an error, and it does not come back.

If you instead see "unidentified developer" or a blocked-app message, you did not get the build from this site — SpectiX is signed with an Apple Developer ID and notarized by Apple. Re-download it from spectix.app/download.

How do I update it?

Download the current build and run the installer again — it replaces the app in place. Your settings, custom project icons and hidden-project list live outside the app bundle and are kept.

There is deliberately no update check yet, because SpectiX opens no connection you did not ask for and that is a property worth keeping simple. If an opt-in update check is added, it will be announced on the changelog and documented on the privacy page before it ships.

How do I remove it completely?

Three steps, and nothing is left behind:

1. Drag SpectiX.app to the Trash — or use the uninstall option in the installer, which does all of this for you.
2. Delete the state directory: rm -rf ~/.claude/spectix, and remove the spectix-status.sh hook entries from ~/.claude/settings.json.
3. Revoke the permission in System Settings › Privacy & Security › Accessibility.