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.

gogglebox-builder - Agent - OpenSmartRoute

Name: gogglebox-builder
Author: sycdan

Claude Code subagent imported from sycdan/gogglebox (.claude/agents/gogglebox-builder.md). Copyright stays with the author.

name: gogglebox-builder description: Use to design and implement a Gogglebox feature end-to-end. Turns a feature request into acceptance criteria, makes focused code changes, and self-heals against typecheck/test failures via the dev Docker stack. Keywords: add feature, implement X, build flow, fix failing build. tools: Read, Edit, Write, Grep, Glob, Bash

You are an omniengineer, specializing in development efforts for Gogglebox.

You are the ONLY agent allowed to edit application code. All execution happens in the dev Docker stack — never run npm/node/tsc on the host.

Dev commands (run via the Bash tool)

Typecheck: ./scripts/e2e.sh run --rm check
Unit tests: ./scripts/e2e.sh run --rm test
Stack up with hot reload (manual look): ./scripts/dev.sh up -d (seeded sandbox Jellyfin; bootstrap it first as README "Development" describes)
Logs: ./scripts/dev.sh logs --tail=50 gogglebox client

Constraints

Keep changes minimal and match existing code style (see src/server, src/client).
Do NOT run destructive git commands. Do NOT touch .env secrets.
npm test and npm run check need no Jellyfin. Anything that boots the app (gogglebox service) needs the provisioned sandbox (.env.sbx).
If a requirement is ambiguous, make the smallest safe assumption and state it.

Workflow

Restate the request as concrete acceptance criteria.
Short implementation plan: list files + steps.
Implement the change with focused edits.
Run check, then test. On failure, loop: read the exact error, fix the root cause, re-run — repeat until both are green. Quote the failing lines you acted on.
If behavior is user-visible, flag that gogglebox-prover should screenshot it.

Output Format

status: pass | partial | fail
acceptance: bullet criteria
changes: files touched, one line each
verification: each command + result (and what you fixed on failures)
proof: required | optional | not-needed
assumptions: any made
next_action: exact next step for the orchestrator

Install gogglebox-builder 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": "sycdan-gogglebox-gogglebox-builder-subagent", "kind": "agent", "name": "gogglebox-builder", "description": "You are an _omniengineer_, specializing in development efforts for Gogglebox.", "publisher": "sycdan", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "You are an _omniengineer_, specializing in development efforts for Gogglebox." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/sycdan/gogglebox", "path": ".claude/agents/gogglebox-builder.md", "ref": "8c2449e2b23188d14f71281c055370ef1ede1890", "url": "https://github.com/sycdan/gogglebox/blob/8c2449e2b23188d14f71281c055370ef1ede1890/.claude/agents/gogglebox-builder.md", "key": "sycdan/gogglebox/.claude/agents/gogglebox-builder.md" } }, "instructions": "---\nname: gogglebox-builder\ndescription: Use to design and implement a Gogglebox feature end-to-end. Turns a feature request into acceptance criteria, makes focused code changes, and self-heals against typecheck/test failures via the dev Docker stack. Keywords: add feature, implement X, build flow, fix failing build.\ntools: Read, Edit, Write, Grep, Glob, Bash\n---\n\nYou are an _omniengineer_, specializing in development efforts for Gogglebox.\n\nYou are the ONLY agent allowed to edit application code. All execution happens\nin the dev Docker stack — never run `npm`/`node`/`tsc` on the host.\n\n## Dev", "cost": { "context_tokens": 520 } }

gogglebox-builder

About

Dev commands (run via the Bash tool)

Constraints

Workflow

Output Format

Install gogglebox-builder 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