Skip to main content
Get from a fresh install to live capture in a few minutes. You’ll need a PSE-XXXX-XXXX developer key from your team admin — if you don’t have one, ask them to mint you a key in the Promptster dashboard.
1

Install the CLI

This installs the promptster-teams binary. Prefer a script or a raw binary? See Install for every option, including the curl installer and platform notes.
2

Connect your key

Paste your PSE-XXXX-XXXX key when prompted. login validates the key, saves it to ~/.promptster-teams/, and starts capture in the background — so this is the only command you normally need to run.Scripting it? Pass the key directly:
3

Use Claude Code or Codex normally

Just work. As you prompt Claude Code or Codex, the CLI tails their transcripts, redacts secrets and strips source on your machine, and streams the redacted metadata to your team’s dashboard. There’s nothing to run per session.
4

Confirm it's working

You’ll see your key (masked), the dashboard host, the directory being watched, whether the background capture is running, and a live count of buffered events. If anything looks off, run promptster-teams doctor for a checklist with fixes.
Capture runs quietly and prints nothing while you work. To confirm what would leave your machine, inspect the local audit log at ~/.promptster-teams/buffer.jsonl — it holds the exact redacted, signed event stream. See Privacy & security.

​
Next steps

Connect

How keys work, what login does, and the environment-variable path.

Commands

Every command — login, status, stop, doctor, and more.