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.

sswa-archive - Prompt - OpenSmartRoute

Name: sswa-archive
Author: Kieransaunders

Prompt file imported from Kieransaunders/sswa (.cursor/commands/sswa-archive.md). Copyright stays with the author.

Archive the SSWA change: ${1:-the active change}. Read single-feature-flow and openspec-conventions first.

Preflight

Run the environment + symlink preflight.
Confirm the change's PR is merged to main. If it isn't, stop — the change must be shipped first (/sswa:verify, then merge).

Steps

Sync specs: run the /sswa:sync logic — merge the change's delta specs into openspec/specs/ (apply order RENAMED → REMOVED → MODIFIED → ADDED).

Move the change folder:

git checkout main && git pull
mkdir -p openspec/changes/archive
git mv openspec/changes/<change-name> openspec/changes/archive/<YYYY-MM-DD>-<change-name>

Use today's date (DD/MM/YYYY in prose, but the folder prefix is ISO YYYY-MM-DD).

Commit the spec merge + archived folder on main (or via a small follow-up PR if your repo protects main).
Clean up the branch:
```
git branch -d sswa/<change-name>
git push origin --delete sswa/<change-name>
```
If the change was built in a worktree (concurrent-agent case), remove that instead of a plain branch delete: git worktree remove ../<repo>-<change-name>.
Optional repo hygiene sweep: offer to run the repo-wide tidy-up from single-feature-flow → Repo hygiene sweep — prune other merged branches (local + remote), dead worktrees left by concurrent-agent runs, and orphaned stashes. It is destructive: survey → classify shipped vs live → get explicit sign-off before deleting. Never prune a branch with an open PR or the worktree this session runs in. Skip entirely if the user declines.
Report and loop: confirm the source-of-truth specs now reflect the shipped behavior, then prompt the next feature: /sswa:propose <next idea>. One feature at a time — so say we all.

Install sswa-archive 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": "Archive the SSWA change: ${1:-the active change}. Read `single-feature-flow` and\n`openspec-conventions` first.\n\n## Preflight\n- Run the environment + symlink preflight.\n- **Confirm the change's PR is merged to `main`.** If it isn't, stop — the change must be\n shipped first (`/sswa:verify`, then merge).\n\n## Steps\n1. **Sync specs:** run the `/sswa:sync` logic — merge the change's delta specs into\n `openspec/specs/` (apply order RENAMED → REMOVED → MODIFIED → ADDED).\n2. **Move the change folder:**\n ```bash\n git checkout main && git pull\n mkdir -p openspec/changes/archive\n git mv openspec/changes/<change-name> openspec/changes/archive/<YYYY-MM-DD>-<change-name>\n ```\n Use today's date (DD/MM/YYYY in prose, but the folder prefix is ISO `YYYY-MM-DD`).\n3. **Commit** the spec merge + archived folder on `main` (or via a small follow-up PR if\n your repo protects `main`).\n4. **Clean up the branch:**\n ```bash\n git branch -d sswa/<change-name>\n git push origin --delete sswa/<change-name>\n ```\n If the change was built in a worktree (concurrent-agent case), remove that instead of a\n plain branch delete: `git worktree remove ../<repo>-<change-name>`.\n5. **Optional repo hygiene sweep:** offer to run the repo-wide tidy-up from\n `single-feature-flow` → **Repo hygiene sweep** — prune *other* merged branches (local +\n remote), dead worktrees left by concurrent-agent runs, and orphaned stashes. It is\n **destructive: survey → classify shipped vs live → get explicit sign-off before\n deleting.** Never prune a branch with an open PR or the worktree this session runs in.\n Skip entirely if the user declines.\n6. **Report and loop:** confirm the source-of-truth specs now reflect the shipped behavior,\n then prompt the next feature: `/sswa:propose <next idea>`. One feature at a time —\n *so say we all.*", "variables": [], "notes": "Close out a merged change — sync its specs into the source of truth, move it to archive, delete the branch, ready the next feature. (mirrors /opsx:archive) Tools: Bash, Read, Write, Edit, Grep, Glob. Arguments: [change-name].", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/Kieransaunders/sswa", "path": ".cursor/commands/sswa-archive.md", "ref": "7b5f40c7c84cf1b6ae66161b3ccc08c9ec9f8e28", "url": "https://github.com/Kieransaunders/sswa/blob/7b5f40c7c84cf1b6ae66161b3ccc08c9ec9f8e28/.cursor/commands/sswa-archive.md", "key": "Kieransaunders/sswa/.cursor/commands/sswa-archive.md" } } }

sswa-archive

About

Preflight

Steps

Install sswa-archive 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