Skip to main content
Yes — the Promptster CLI, one command:
Or via npm: npm install -g @promptster/cli. See Install.
Claude Code, Codex, and Cursor. promptster start asks which one you’ll use (or pass --tools). Open that tool from the workspace directory and run promptster doctor to confirm everything is wired up.
In the default managed mode, no — your tool is routed through the Promptster proxy and your personal account is never billed. Some assessments instead have you use your own Claude Code, Codex, or Cursor sign-in; promptster start sets up whichever mode the assessment uses. See Signing in to the AI.
No. In managed mode, Promptster’s proxy out-ranks a logged-in Max/Pro subscription automatically, so you can stay signed in. The only thing that interferes is an ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN exported in your shell — promptster doctor flags it, and eval "$(promptster env --clear)" clears it. See Signing in to the AI.
That’s fine. Promptster captures what happens in your session; if you use AI less, fewer AI events are recorded — that isn’t penalized. You’re evaluated on judgment, not AI volume.
Almost always because your tool wasn’t opened from the workspace directory, so capture never attached. Quit and reopen Claude Code, Codex, or Cursor from inside the workspace (or use promptster start --restart). Full walkthrough: my events aren’t being captured.
Yes. Your session stays open until you run promptster done (or the time limit ends). Stop and restart your editor or machine freely — just reopen the editor from the workspace so hooks reload. Run promptster status to see where you left off.
Timed assessments auto-submit server-side when the window closes, so you won’t lose captured work. Check remaining time with promptster brief, and submit deliberately with promptster done before time’s up if you can.
Keep working — events are written to a local buffer as they happen, so a brief drop won’t interrupt you. Confirm the server is receiving events with promptster status. If a disconnect hits during promptster done, the upload fails loudly (no false “submitted”) — just re-run done once you’re back online.
It bundles and uploads your workspace, flushes remaining events, marks your session complete, and gives you a link to your own session replay (copied to your clipboard). It then cleans up your tool’s hooks and, in managed mode, the proxy config. If you have empty decision notes, it asks you to finish them first (or pass --auto).
Keys expire after a window set by the hiring team. Run promptster brief to see time remaining. If your key has expired, promptster doctor will say so — ask the hiring team for a fresh one.
Not strictly, but it’s one of the highest-signal parts of your submission. Use /explain in Claude Code or promptster explain to record why you made a choice. The CLI nudges you after a chunk of work if you haven’t explained anything recently. See Decisions.
Yes — after submitting, promptster done gives you a private replay link. You can also request a full data export via the hiring team or [email protected]. See Privacy & Data.
Run promptster reset to wipe local session state and hooks (keeping the binary), then promptster start PST-XXXX-XXXX again. It works even when the session file is corrupt. See Recovering from a broken setup.