Documentation
Configuration
Providers, thresholds, prompt versions, and credentials — every key has a built-in default; you override only what you need.
Configuration lives in .careeros/config.yaml. Every key has a
built-in default, so you only set what you want to change.
careeros config prints the fully resolved configuration.
Providers
The providers block controls which sources are enabled and the
order they run in. Deduplication keeps the first occurrence of a role, so
list your most-trusted source first. As of v1.9, discovery runs on
ats-dataset: a free, open, no-signup dataset covering 65
real ATS platforms, filtered from your own profile.yaml.
Several earlier sources, including a paid REST aggregator, were tried
and superseded — see the project's providers/README.md for
the evidence, and how to re-enable any of them.
providers: ats-dataset: { enabled: true } # free, no signup — your main source fantastic-jobs: { enabled: false } # optional paid alternativeThresholds
Two tiers decide what happens to an evaluated job. Apply-tier gets the full pipeline; Consider-tier gets a Sheet row only. Below the consider threshold, a job is omitted.
threshold: 4.0 # Apply: full artifacts + Sheet rowconsider_threshold: 3.5 # Consider: Sheet row only (score + reason)gate_batch_size: 50 # jobs per gate call — the main cost leverPrompt versions
Each reasoning stage points at a versioned prompt file. Because the version is part of every cache fingerprint, changing one line here regenerates only that stage.
prompts: gate: v1 eval: v2 resume: v4 cover: v2Credentials
Secrets never go in config. They live in .careeros/secrets.env
(gitignored), and config fields reference the environment variable
name. This is why the Sheets service account and the Drive OAuth
client are set by pointing at env vars, not by pasting keys. The default
discovery source needs none of this — the block below only applies if
you've enabled the optional paid Fantastic Jobs provider.
FANTASTIC_API_KEY=... # or RAPIDAPI_KEY, depending on api.transportGoogle Sheets and Drive
Sheets uses a service account — you must share your Sheet with the service account's email, which is the step people miss. Drive uses a different credential (an OAuth desktop client), because files land in your own Drive. Both are one-time setups, and Drive is entirely optional and off by default.