One command. Then just code.
Connect Claude Code or Codex without editing JSON or moving tokens around.
Choose your agent
Sign in and open Privacy & agents. Choose Connect Codex or Connect Claude Code. Metadata keeps prompt text private; redacted mode includes filtered text.
Copy your setup command
Run it in the environment where your agent runs: your Mac, Linux terminal, WSL, SSH host, or dev container. Node.js 22+ and curl are required. No repository checkout or npm package is needed.
Restart your agent and submit a prompt
For Codex, open /hooks to review and trust the installed definitions. For Claude Code, restart it to load the hooks. The dashboard distinguishes installation from the first prompt actually received.
Fits your environment.
The installer uses your current Node executable, so the hooks don’t depend on the agent’s PATH. Custom CODEX_HOME and CLAUDE_CONFIG_DIR locations are respected.
It backs up existing settings, merges only PromptGolf’s three hooks, and preserves your permissions, plugins, and other hooks. It refuses malformed JSON and symlinked configuration files.
Run setup separately in each environment. For dev containers, persist your home/config directories and run setup inside the container.
Private from the start.
Your setup command expires after five minutes and works once. The capture-only token is stored in ~/.promptgolf/AGENT/client.json with private file permissions. No API key is installed.
Tokens expire after 30 days. Generate a new setup command to renew; the installer revokes the previous token after successful installation. Disconnect devices from the dashboard whenever you need.
No transcript, repository file, tool argument, or tool output is opened or uploaded. Redaction is best effort; choose metadata when prompt text must stay private.
Check or remove a connection.
These commands check the collector and hook registration, or remove only PromptGolf’s hooks. Replace codex with claude-code for Claude Code.
node "$HOME/.promptgolf/codex/connect.mjs" doctor --agent codex node "$HOME/.promptgolf/codex/connect.mjs" uninstall --agent codex
Uninstall also revokes the device token when the service is reachable. If you are offline, disconnect the device in the dashboard later. Codex trust and a prompt received from the actual agent are separate from the installer’s connectivity check.
Chrome, in three steps.
Download the extension from the dashboard, extract it, and use Load unpacked in chrome://extensions with Developer mode enabled. Sign in to PromptGolf and paste the session pairing token from Workspace settings into the extension.
Chrome Web Store installation will replace this preview workflow after the extension is published. Browser sites stay opt-in.
What the current hooks measure.
Prompt submissions, tool categories, and turn stops are linked into coding runs. Mark whether the result worked to measure outcomes. A stop event does not prove success.
These hooks do not provide authoritative agent billing or token usage. Native filtered OpenTelemetry ingestion is not implemented yet, so real coding-agent cost remains unavailable.
Collector analysis runs privately on the service. Prompt lab evaluation sends only explicitly selected text to the configured evaluator; on-prem deployments can use a local compatible evaluator or disable AI evaluation.