Config Variants

Config variants

config.yaml is the active run profile. For experiments — a different dataset, model, agent version, concurrency, or retry setting — create a separate variant file next to it instead of editing the active one:

config.glm5-smoke.yaml
config.<dataset>.<agent>.yaml

Only replace config.yaml when you are ready to make a variant active. Each launched job should include a snapshot of the active config at:

artifacts/jobs/<job>/config.yaml

so a run can always be reproduced from its own snapshot.

Tunable parameters

The knobs worth tuning between runs all live under runtime_info.input in config.yaml:

Parameter	Meaning
`agent.temperature`	Agent sampling temperature (0.0-1.0)
`agent.max_turns`	Maximum agent turns per task
`harbor_job.n_concurrent`	Harbor concurrent rollouts
`harbor_job.n_tasks`	Maximum tasks selected for this job; `null` means all
`harbor_job.timeout_multiplier`	Per-task timeout multiplier
`sft_conversion.tokenizer_name`	Tokenizer used for LF statistics; align it with trainer

Changing agent.name requires an internally consistent preset: import path, API protocol, version, runtime image/host path, and an explicit conversion scaffold when automatic mapping is unavailable.

Build and deploy the docs site

These docs are a fumadocs (Next.js) site under docs/, statically exported and served from Cloudflare Pages.

Requirements

The site needs Node >= 20. If the host's system Node is older, activate a newer release through nvm before building:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
nvm use 22

Build locally

cd docs
npm install
npm run build     # static export to docs/out/

next.config.mjs sets output: 'export', so the build emits a static out/ directory. The root redirect (/ -> /docs) is expressed in public/_redirects rather than Next's redirects(), which static export disables.

Deploy to Cloudflare Pages

docs/deploy_cloudflare_pages.sh builds and deploys to a dedicated Cloudflare Pages project (swe-tracer-docs), separate from the dashboard's swe-tracer-databoard project:

bash docs/deploy_cloudflare_pages.sh

It activates Node 22 via nvm, runs the static build, and deploys docs/out/ with wrangler pages deploy. It reads CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID from the environment or ENV_FILE (default ~/.config/trajgen_progress_cloudflare.env).

The docs target defaults to swe-tracer-docs. Use DOCS_PROJECT_NAME / DOCS_BRANCH_NAME inside a shared dashboard env file, or set PROJECT_NAME / BRANCH_NAME before invocation. Dashboard target variables loaded from the shared file are intentionally ignored so a docs deploy cannot overwrite the dashboard.