Skip to content
Documentation menu

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. Three free-and-direct core sources are on by default; the paid Apify-backed sources ship disabled.

.careeros/config.yaml
providers:
fantastic-jobs: { enabled: true } # core — your main source
remoteok: { enabled: true } # core — free, no signup
we-work-remotely: { enabled: true } # core — free, no signup
# paid, opt-in, off by default:
naukri: { enabled: false }
glassdoor: { enabled: false }
ziprecruiter: { enabled: false }
indeed: { enabled: false }
foundit: { enabled: false }

Thresholds

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.

.careeros/config.yaml
threshold: 4.0 # Apply: full artifacts + Sheet row
consider_threshold: 3.5 # Consider: Sheet row only (score + reason)
gate_batch_size: 50 # jobs per gate call — the main cost lever

Prompt 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.

.careeros/config.yaml
prompts:
gate: v1
eval: v2
resume: v1
cover: v1

Credentials

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.

.careeros/secrets.env
FANTASTIC_API_KEY=...
APIFY_TOKEN=... # only if you enable a paid provider

Google 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.