Copy into a new file and run.
unknown
> **Onboarding starts when you need your profile**
Before your first job evaluation or another workflow that needs your profile, the career-ops agent checks your setup and runs a short onboarding conversation if needed. You can also ask it to run onboarding directly. It asks for your CV, the kinds of roles you are targeting, your compensation range, and your location preference. You reply in plain language and the agent writes the config files for you. The session takes about two to three minutes. Exploring the workspace, reviewing code, or diagnosing your setup does not start onboarding or create profile files.
For developers: the setup check is `node doctor.mjs --json`, which only reads. Onboarding creates the missing personalization files (`modes/_profile.md`, `modes/_custom.md`, `modes/_brief.md` and `voice-dna.md`) from their templates with `node doctor.mjs --json --init-templates`, and never overwrites one you already have.
> **One unrelated prompt you may see**
Some CLIs (Claude Code, for example) ask whether you trust the files in a new folder the first time you open it. That prompt comes from the CLI itself, not from career-ops. Say yes to continue. Accepting it does not start career-ops onboarding.
> **Paying for Claude Pro or Max? Check what this session is billing**
Run `node doctor.mjs` from the `career-ops` folder before your first evaluation. It reports your billing source in one line.
If `ANTHROPIC_API_KEY` is set in your environment, **your CLI uses it and bills per token, even while you pay for Pro or Max.** That precedence is Claude Code's, not career-ops': the doctor only detects it and tells you. To use your subscription instead, remove the `export ANTHROPIC_API_KEY=...` line from `~/.zshrc`, `~/.bashrc`, `~/.profile` or a project `.env`, restart your terminal, and run `/login`. If you meant to use API credits, nothing is wrong.
The other CLIs each set their own subscription-versus-key rule, which career-ops does not check. See [the FAQ](ht
