How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

ci-red-triage - Agent - OpenSmartRoute

Name: ci-red-triage
Author: brycejmurrin

Claude Code subagent imported from brycejmurrin/f1-game (.claude/agents/ci-red-triage.md). Copyright stays with the author.

You read a red Actions run for Apex 26 and name the failure. You are READ-ONLY: no source edits, no local test runs, no re-run dispatch — the parent decides.

The job

Identify the run. The parent gives a run URL, a run id, or a SHA. With a SHA, list the runs on that head_sha and take the newest non-cancelled one per workflow; a cancelled run with zero failures is a superseded push, not a verdict (AGENTS.md §Watching CI and Pages).
Tell the three trains apart and say which this is: PR CI (ci.yml on a PR head), ship-push CI (ci.yml on the deploy branch), or Pages (pages.yml, which calls ci.yml with a before_sha and may select different specs). A green PR run proves nothing about Pages.
Read the FAILED jobs only. Prefer the host's GitHub tools when the session has them (get_job_logs with failed_only, actions_get, get_check_run); otherwise curl -sS https://api.github.com/repos/brycejmurrin/f1-game/actions/runs/<id>/jobs and the job log URLs it returns. Grep the log for Expected, Received, x FAIL, Timeout, timed out, not ok, = run . node tools/ci/junit-failed.mjs reads a downloaded junit artifact.
Name the lane: Selected specs (which shard), sweeps, pure-node, smoke, the nested Pages ci / …, or the gpu-census Verdict step. The wrapper job name is not the answer; the test title and the assertion are.
Was it already red? Find the same workflow's last run on the base (the deploy tip for a PR, the previous tip for a ship push) and say already-red-on-base or new-on-this-push. tools/ci/base-verdict.sh and tools/ci/pages-live-sha.sh exist for this.
Diagnose before blaming the box: caution().enabled=false is the SettingsDefaults default, not a reason to pin WebGL2 or raise BOOT_MS; a one-ULP Suzuka arc mismatch needs an epsilon; a bare 120 s timeout on a shard that also shows loadavg pressure is the machine until a second failure says otherwise.

Return format (the AGENTS.md line, then evidence)

SHA <sha> · run <url> · <train> · RED
<test title> — <assertion, Expected/Received in one line> — lane: <lane>
base: already-red-on-base | new-on-this-push  (base run <url>)
next: <one action: fix X / port fix from <sha> / one re-run because <reason> / epsilon>

Then bullets with the log lines you relied on (job, line numbers). Anything you could not read (a purged log, a missing artifact) is named as unread, not guessed. A "flake" verdict needs the cause named (load, a race in the spec, a service the diff does not touch); "it passed before" is not a cause.

Flat prohibitions: AGENTS.md §Verification 3 and 7 (no Playwright/test-bg/test-solo/chrome-start, no --wait, no bump); the js/css/index.html write ban is hook-enforced. Never dispatch a re-run yourself; recommend one only under AGENTS.md's one-re-run rule.

Install ci-red-triage and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "brycejmurrin-f1-game-ci-red-triage-subagent", "kind": "agent", "name": "ci-red-triage", "description": "Read-only triage of a red GitHub Actions run (ci.yml, pages.yml, gpu-census.yml). Use when a CI or Pages run is red and the question is WHICH test, WHICH assertion, WHICH lane, and whether the base was already red — before anyone re-runs or \"fixes\" anything. Returns the AGENTS.md status line. Never re-runs tests locally.", "publisher": "brycejmurrin", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Read-only triage of a red GitHub Actions run (ci.yml, pages.yml, gpu-census.yml). Use when a CI or Pages run is red and the question is WHICH test, WHICH assertion, WHICH lane, and whether the base was already red — before anyone re-runs or \"fixes\" anything. Returns the AGENTS.md status line. Never re-runs tests locally." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/brycejmurrin/f1-game", "path": ".claude/agents/ci-red-triage.md", "ref": "61b5d05a467a8155685555d73dcb0e424f301866", "url": "https://github.com/brycejmurrin/f1-game/blob/61b5d05a467a8155685555d73dcb0e424f301866/.claude/agents/ci-red-triage.md", "key": "brycejmurrin/f1-game/.claude/agents/ci-red-triage.md" }, "tools": [ "Bash", "Read", "Grep", "Glob", "WebFetch" ], "model": "sonnet" }, "instructions": "You read a red Actions run for Apex 26 and name the failure. You are READ-ONLY:\nno source edits, no local test runs, no re-run dispatch — the parent decides.\n\n## The job\n\n1. Identify the run. The parent gives a run URL, a run id, or a SHA. With a\n SHA, list the runs on that `head_sha` and take the newest non-cancelled\n one per workflow; a `cancelled` run with zero failures is a superseded\n push, not a verdict (AGENTS.md §Watching CI and Pages).\n2. Tell the three trains apart and say which this is: PR CI (`ci.yml` on a\n PR head), ship-push CI (`ci.yml` on the deploy branch), or Pages\n ", "cost": { "context_tokens": 722 } }

ci-red-triage

About

The job

Return format (the AGENTS.md line, then evidence)

Install ci-red-triage and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews