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.

wrap-up - Prompt - OpenSmartRoute

Name: wrap-up
Author: tungdtfgw

Prompt file imported from tungdtfgw/note-app-demo-copilot (.github/prompts/wrap-up.prompt.md). Copyright stays with the author.

Wrap Up Session

Your job is to update AGENTS.md with a concise summary of what happened in this session.

Steps

Run git diff --stat and git log --oneline -10 to see what changed.
Scan the conversation history for architecture decisions, new patterns, or TODOs mentioned.
Update the following sections in AGENTS.md at the project root:

Current State

Update the phase and status to reflect where the project is now.

Architecture Decisions

Append any new decisions made in this session (one line each).
Format: - **Decision:** reason (YYYY-MM-DD)

Recent Changes

Replace the content with a brief summary of this session's work.
Format: bullet list, max 5 items, each under 80 chars.
Include the date: ### Session YYYY-MM-DD

TODOs

Check off completed items.
Add new TODOs discovered during the session.

Rules

Keep AGENTS.md under 80 lines total. Remove outdated entries if needed.
Be concise — one line per item, no paragraphs.
Do NOT touch .github/copilot-instructions.md — that file is fixed.
Show me the proposed changes before writing.

# Wrap Up Session Your job is to update `AGENTS.md` with a concise summary of what happened in this session. ## Steps 1. Run `git diff --stat` and `git log --oneline -10` to see what changed. 2. Scan the conversation history for architecture decisions, new patterns, or TODOs mentioned. 3. Update the following sections in `AGENTS.md` at the project root: ### Current State - Update the phase and status to reflect where the project is now. ### Architecture Decisions - Append any new decisions made in this session (one line each). - Format: `- **Decision:** reason (YYYY-MM-DD)` ### Recent Changes - Replace the content with a brief summary of this session's work. - Format: bullet list, max 5 items, each under 80 chars. - Include the date: `### Session YYYY-MM-DD` ### TODOs - Check off completed items. - Add new TODOs discovered during the session. ## Rules - Keep `AGENTS.md` **under 80 lines** total. Remove outdated entries if needed. - Be concise — one line per item, no paragraphs. - Do NOT touch `.github/copilot-instructions.md` — that file is fixed. - Show me the proposed changes before writing.

Install wrap-up 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": "# Wrap Up Session\n\nYour job is to update `AGENTS.md` with a concise summary of what happened in this session.\n\n## Steps\n\n1. Run `git diff --stat` and `git log --oneline -10` to see what changed.\n2. Scan the conversation history for architecture decisions, new patterns, or TODOs mentioned.\n3. Update the following sections in `AGENTS.md` at the project root:\n\n### Current State\n- Update the phase and status to reflect where the project is now.\n\n### Architecture Decisions\n- Append any new decisions made in this session (one line each).\n- Format: `- **Decision:** reason (YYYY-MM-DD)`\n\n### Recent Changes\n- Replace the content with a brief summary of this session's work.\n- Format: bullet list, max 5 items, each under 80 chars.\n- Include the date: `### Session YYYY-MM-DD`\n\n### TODOs\n- Check off completed items.\n- Add new TODOs discovered during the session.\n\n## Rules\n- Keep `AGENTS.md` **under 80 lines** total. Remove outdated entries if needed.\n- Be concise — one line per item, no paragraphs.\n- Do NOT touch `.github/copilot-instructions.md` — that file is fixed.\n- Show me the proposed changes before writing.", "variables": [], "notes": "Summarize session changes and update AGENTS.md Tools: runInTerminal, search/codebase, read, edit.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/tungdtfgw/note-app-demo-copilot", "path": ".github/prompts/wrap-up.prompt.md", "ref": "5eef8ac5021e06aeb87c4d1e8ec9ea2714c34b0c", "url": "https://github.com/tungdtfgw/note-app-demo-copilot/blob/5eef8ac5021e06aeb87c4d1e8ec9ea2714c34b0c/.github/prompts/wrap-up.prompt.md", "key": "tungdtfgw/note-app-demo-copilot/.github/prompts/wrap-up.prompt.md" } } }

wrap-up

About

Wrap Up Session

Steps

Current State

Architecture Decisions

Recent Changes

TODOs

Rules

Use it

Install wrap-up 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