Skip to main content

Configuration keys

Agentic Pipeline is on by default. Keys exist to opt a repository OUT of a capability or to name a repo-specific value. Per-repo keys are spelled slipstream.<setting>.<owner>/<repo>.

Write path

The only agent write path is slipstream_onboard {"action":"set","updates":{...}}. It accepts exactly these shapes; production-affecting enables ask for confirm: true, and turning something off or clearing it never asks:

KeyValuesConfirm to setWhat it does
slipstream.reposappend owner/repoyesAdds a repository to the fleet allowlist (append-only).
slipstream.mode.<owner>/<repo>shadow / candidateyesHow this repo's check behaves: shadow posts a non-required check while the repo soaks, candidate posts the required one. No other value is accepted.
slipstream.ship.<owner>/<repo>1 / 0yesShip-on-green: a green check on main enqueues the deploy recipe. Landing a valid .slipstream-deploy.json turns this ON automatically; set 0 to opt out.
slipstream.ship_mode.<owner>/<repo>native / dispatchyesHow the deploy executes: native runs the repo's own deploy recipe on Agentic Pipeline; dispatch (the default when unset) fires the repo's publish workflow instead.
slipstream.deploy_recipe.<owner>/<repo>pathyesOverrides the deploy recipe location.
slipstream.automerge.<owner>/<repo>1 / 0yesLets Agentic Pipeline arm auto-merge on recipe PRs it opens.
slipstream.live_url.<owner>/<repo>URLnoHealth URL probed after a deploy before live is claimed.
slipstream.version_url.<owner>/<repo>URLnoEndpoint that returns the live version so slipstream_fleet_status can prove the deployed sha.
slipstream.version_stage.<owner>/<repo>stage namenoWhich deploy stage publishes the version.

Everything else is platform-managed. slipstream_onboard {"action":"get"} prints the current values plus a readiness report.

Keys you will read but cannot set here

KeyMeaning when you see it
slipstream.auto_scope.<owner>/<repo>annotate / enforce / off — see Auto-scope. Graduation to enforce is automatic; a row here (any value) freezes it.
slipstream.proof_reuse.<owner>/<repo>Stage proof reuse, opt-in per repo (the one declared exception to default-ON).
slipstream.canary_repoThe platform's own heartbeat repo; its runs are synthetic.
slipstream.executor_fence_allow_repoRepo admitted during a fenced release for the canary check.

If a tool tells you to set a key not listed under Write path, that key is platform-only: file it through the platform's feedback channel instead of retrying.