Skip to main content
Your developer key is the whole identity. There’s no OAuth flow, no browser login, and no org code to enter — a single PSE-XXXX-XXXX key connects you to your team. An admin mints it in the Promptster dashboard and sends it to you.

​
Connect with login

The simplest path is one command:
It prompts for your key, or you can pass it directly for scripted setup:
login:
  1. Validates the key format.
  2. Best-effort pings your dashboard host to confirm it’s reachable.
  3. Saves your key to ~/.promptster-teams/credentials (readable only by you).
  4. Starts capture in the background, scoped to your home directory — so all your repos are covered.
That’s it. You don’t run login again unless you get a new key.
Some older onboarding snippets set an environment variable and run watch directly and don’t mention login. login is the recommended path — it also starts background capture for you. The environment-variable path below still works if you prefer it.

​
The environment-variable path

If you’d rather not store the key on disk — for example in an ephemeral or CI-like environment — set it in your environment and start capture yourself:
Point the CLI at a non-default dashboard host with --api-url or PROMPTSTER_TEAMS_API_URL. See Configuration for the full precedence order and every variable.

​
Choosing what gets watched

By default, login watches your entire home directory, so every repo you work in is captured. If you start capture manually from inside a specific project, only that directory (and its git worktrees) is watched — transcripts whose working directory sits outside the watched path are skipped. To set the scope explicitly:
If capture seems to record nothing, the most common cause is scope: the AI tool’s transcript reports a working directory that isn’t inside the watched directory. Run promptster-teams status to see the watched directory, and re-run login (which defaults the scope to your home directory) if it’s too narrow.

​
Verify the connection

doctor confirms your key is present and valid, your dashboard host is reachable, and your Claude Code transcript directory exists. See Commands and Troubleshooting.

​
Getting a key (for admins)

Managers and admins mint and revoke per-developer keys in the Promptster dashboard, where each active developer uses one seat. Hand the PSE-XXXX-XXXX key to the engineer; they run login once. Revoking a key stops that developer’s capture from being accepted.