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.

README - Prompt - OpenSmartRoute

Prompt file imported from wewececetw/task-router (.codex/prompts/README.md). Copyright stays with the author.

Codex Prompts

These files adapt the legacy .claude/commands/ guidance for Codex. Canonical shared routing rules live in agent-profiles/shared/routing-rules.md.

Codex does not need Claude slash-command frontmatter to perform the work. Use these prompt files as operational playbooks when Barron asks for the matching task by name.

Prompt Map

local.md: send a lightweight task to the local oMLX model.
implement-simple.md: use the local model for boilerplate-style tasks, then review and patch the result.
maintenance.md: changelog, docstring, i18n, migration, and test-stub flows.
speckit.md: Codex handling for Spec Kit workflows.
openspec.md: Codex handling for Fission-AI/OpenSpec workflows.

Legacy Claude files remain in .claude/commands/ for reference and backward compatibility.

Generated global Codex installs should come from agent-profiles/codex/ so the Codex and Claude Code profiles stay semantically aligned.

# Codex Prompts These files adapt the legacy `.claude/commands/` guidance for Codex. Canonical shared routing rules live in `agent-profiles/shared/routing-rules.md`. Codex does not need Claude slash-command frontmatter to perform the work. Use these prompt files as operational playbooks when Barron asks for the matching task by name. ## Prompt Map - `local.md`: send a lightweight task to the local oMLX model. - `implement-simple.md`: use the local model for boilerplate-style tasks, then review and patch the result. - `maintenance.md`: changelog, docstring, i18n, migration, and test-stub flows. - `speckit.md`: Codex handling for Spec Kit workflows. - `openspec.md`: Codex handling for Fission-AI/OpenSpec workflows. Legacy Claude files remain in `.claude/commands/` for reference and backward compatibility. Generated global Codex installs should come from `agent-profiles/codex/` so the Codex and Claude Code profiles stay semantically aligned.

Install README 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.

README

About

Codex Prompts

Prompt Map

Use it

Install README 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

Manifest

Reviews