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.

persist - Prompt - OpenSmartRoute

Name: persist
Author: albegali

Prompt file imported from albegali/agentic-portal (.codex/prompts/persist.md). Fill in {{arguments}} before use. Copyright stays with the author.

Recommended model: gpt-5-codex (codex -p balanced) (tier balanced, see models.toml). Switch to it before running this command.

Developer mode, ID {{arguments}} (delivery/AGENT_GUIDE.md §5, step 7).

Update the Spec (§11) and only the reference/ docs touched by the story.
RUN: §5 Tuning accepted by (the human who ran /persist, from project.toml owner unless they said otherwise) and Date; §7-10 (§8 as facts: AC n/n, Tests: command → result, out-of-scope changes, CI:); status Persisted (not Closed: review and /close follow). Spec §11 facts and status Done. Tasks split off into new stories (split_from) are listed under §9 Tasks deferred with the new ID.
make gates ID={{arguments}} (writes RUN §8 ### Gates; a failing gate → stop, RUN stays Tuning), make backlog (Spec index), then make check.
Git: the /persist part of delivery/guide/git.md — commit, push the story branch, open its PR (RUN References Branch, PR), wait for the required checks, record CI: in RUN §8 and push it. Merge nothing. Chat: outcome in 3 lines, then /review-story <ID> in a fresh session.

> Recommended model: **gpt-5-codex** (`codex -p balanced`) (tier `balanced`, see models.toml). Switch to it before running this command. Developer mode, ID {{arguments}} (`delivery/AGENT_GUIDE.md` §5, step 7). 1. Update the Spec (§11) and only the `reference/` docs touched by the story. 2. RUN: §5 `Tuning accepted by` (the human who ran `/persist`, from `project.toml` owner unless they said otherwise) and `Date`; §7-10 (§8 as facts: AC n/n, `Tests:` command → result, out-of-scope changes, `CI:`); status `Persisted` (not `Closed`: review and `/close` follow). Spec §11 facts and status `Done`. Tasks split off into new stories (`split_from`) are listed under §9 Tasks deferred with the new ID. 3. `make gates ID={{arguments}}` (writes RUN §8 `### Gates`; a failing gate → stop, RUN stays `Tuning`), `make backlog` (Spec index), then `make check`. 4. Git: the `/persist` part of `delivery/guide/git.md` — commit, push the story branch, open its PR (RUN References `Branch`, `PR`), wait for the required checks, record `CI:` in RUN §8 and push it. Merge nothing. Chat: outcome in 3 lines, then `/review-story <ID>` in a fresh session.

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

{ "prompt": "\n> Recommended model: **gpt-5-codex** (`codex -p balanced`) (tier `balanced`, see models.toml). Switch to it before running this command.\n\nDeveloper mode, ID {{arguments}} (`delivery/AGENT_GUIDE.md` §5, step 7).\n1. Update the Spec (§11) and only the `reference/` docs touched by the story.\n2. RUN: §5 `Tuning accepted by` (the human who ran `/persist`, from `project.toml` owner unless they said otherwise) and `Date`; §7-10 (§8 as facts: AC n/n, `Tests:` command → result, out-of-scope changes, `CI:`); status `Persisted` (not `Closed`: review and `/close` follow). Spec §11 facts and status `Done`. Tasks split off into new stories (`split_from`) are listed under §9 Tasks deferred with the new ID.\n3. `make gates ID={{arguments}}` (writes RUN §8 `### Gates`; a failing gate → stop, RUN stays `Tuning`), `make backlog` (Spec index), then `make check`.\n4. Git: the `/persist` part of `delivery/guide/git.md` — commit, push the story branch, open its PR (RUN References `Branch`, `PR`), wait for the required checks, record `CI:` in RUN §8 and push it. Merge nothing.\nChat: outcome in 3 lines, then `/review-story <ID>` in a fresh session.", "variables": [ "arguments" ], "notes": "Developer mode — persistence/reconciliation, story PR and CI result (RUN → Persisted; nothing merged) Arguments: <ID>.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/albegali/agentic-portal", "path": ".codex/prompts/persist.md", "ref": "0694fcfa6f9f742ee5403ca5c19a53b6c55c6d0c", "url": "https://github.com/albegali/agentic-portal/blob/0694fcfa6f9f742ee5403ca5c19a53b6c55c6d0c/.codex/prompts/persist.md", "key": "albegali/agentic-portal/.codex/prompts/persist.md" } } }

persist

About

Use it

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