Skip to main content
Most engineers never touch configuration — promptster-teams login sets everything up. This page is the full reference for scripted setups, non-default hosts, and debugging.

​
Environment variables

​
How your key and host are resolved

For both your key and your dashboard host, the CLI takes the first value it finds, in this order:
  1. A command-line flag (--key, --api-url)
  2. The matching environment variable
  3. The stored credentials file
  4. The hosted default (for the host)
So a flag always wins over the environment, which wins over the saved file.

​
Config files

Everything lives under ~/.promptster-teams/: Background capture also keeps small watcher state files (process IDs and read offsets) in this directory so it processes each transcript exactly once and can be stopped cleanly.
Never commit ~/.promptster-teams/ or share session.key — that seed is what proves events came from your device.

​
Coexisting with the hiring CLI

If you also have Promptster’s hiring CLI installed, the two don’t interfere. The Teams CLI uses the promptster-teams binary and the ~/.promptster-teams directory; the hiring CLI uses promptster and ~/.promptster. They can run side by side.