promptster-teams status shows whether capture is running and what it’s watching; promptster-teams doctor checks your key, dashboard connectivity, and transcript directories, and prints a fix for each problem.
Capture isn’t recording anything
No developer key configured
No developer key configured
watch or start fails with a message that no developer key is configured. Connect with login, set the environment variable, or pass the key:doctor also flags a key that’s set but isn’t a valid PSE- key.The watched directory is too narrow
The watched directory is too narrow
This is the most common cause of silent capture. The CLI only captures transcripts whose working directory sits inside the watched directory (or one of its git worktrees). If you started capture from a subfolder or
/tmp, your repos are outside the scope.Check the watched directory in status, then re-run login — it defaults the scope to your home directory so all your repos are covered. To set it explicitly:Your AI tool hasn't created a transcript yet
Your AI tool hasn't created a transcript yet
The CLI reads transcript files that Claude Code and Codex write to disk. If a tool has never run, its transcript directory doesn’t exist yet and
doctor reports it. Run the tool once, then check again. Only Claude Code and Codex are supported — Cursor transcripts are not captured.Capture is silent — is it actually running?
Capture is silent — is it actually running?
Background capture prints nothing by design. To watch it work, run in the foreground with debug logging:You’ll see a line per captured event. You can also confirm events are accumulating in
status (the buffered-event count) or by tailing ~/.promptster-teams/buffer.jsonl.Managing the background process
status says capture isn't running
status says capture isn't running
Start it:
start is idempotent, so it’s safe to run even if you’re unsure.stop can't find the process
stop can't find the process
If capture was started without a tracked process ID, Then stop that process. Afterward,
stop no-ops and points you to find it manually:start (or login) gives you a properly tracked background process.Capture looks degraded in the logs
Capture looks degraded in the logs
If a transcript’s format changes or a watcher reads a large chunk without parsing an event, it marks itself degraded; a stale heartbeat is also logged. Check If it persists after an update, contact your admin.
~/.promptster-teams/daemon.log, then restart capture:Connection problems
Dashboard host not reachable
Dashboard host not reachable
doctor reports the host as unreachable. Confirm you’re online and that PROMPTSTER_TEAMS_API_URL (if you set it) points at the right host. The check is a plain request with no auth, so a failure here is network or DNS, not your key.A few events don't show up
A few events don't show up
An occasional event the backend doesn’t recognize is dropped without a retry, and capture stays healthy — that’s expected and harmless. Persistent failures are different: an authentication error (your key was revoked), rate limiting, or a server error will surface as a real problem. Re-run
doctor, and if your key was revoked, ask your admin for a new one.Install snags
Command not found after the script install
Command not found after the script install
Add the bin directory to your Add that line to
PATH and restart your shell:~/.zshrc or ~/.bashrc to make it permanent.Install script fails with a checksum error
Install script fails with a checksum error
The installer verifies the downloaded binary against its checksum and aborts on a mismatch — a safety feature. Retry the install; if it keeps failing, the download may be corrupted or blocked by a proxy. Fall back to the npm install.
Installing on Windows
Installing on Windows
The install script supports macOS and Linux only. On Windows, install with npm: