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.

Update Project Knowledge - Prompt

Name: Update Project Knowledge
Author: LocNguyen2000

Prompt file imported from LocNguyen2000/monorepo-microservice (.github/prompts/update-project-knowledge.prompt.md). Copyright stays with the author.

Update the repository's durable project knowledge based on this conversation and relevant workspace files.

Source and Scope

Use the current conversation for decisions, implementation discoveries, and outcomes. Inspect relevant workspace files when needed to verify facts.
Treat the root PROJECT_KNOWLEDGE.md as the destination. Create it if it does not exist; otherwise update the existing sections in place and remove stale or duplicated facts when clearly superseded.
Record only reusable project knowledge: architecture and ownership, confirmed conventions, important invariants, validated commands, and unresolved follow-up that future work needs to know.
Clearly label unresolved or unverified details. Do not turn assumptions into facts.
Never record secrets, credentials, tokens, personal data, or sensitive values. Do not copy large code blocks or routine chat summaries into the knowledge file.
Do not modify application code, configuration, migrations, or other documentation as part of this task.

Update Process

Identify candidate facts from the conversation, including what changed and what was verified.
Check existing knowledge and relevant files for accuracy, relevance, and duplication.
Make the smallest useful edit to PROJECT_KNOWLEDGE.md, preserving valid existing information and its style.
If the chat produced no durable knowledge, leave the file unchanged and say so.
Report the knowledge topics added, changed, or left unchanged, and note any uncertainty.

Install Update Project Knowledge 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": "Update the repository's durable project knowledge based on this conversation and relevant workspace files.\n\n## Source and Scope\n- Use the current conversation for decisions, implementation discoveries, and outcomes. Inspect relevant workspace files when needed to verify facts.\n- Treat the root `PROJECT_KNOWLEDGE.md` as the destination. Create it if it does not exist; otherwise update the existing sections in place and remove stale or duplicated facts when clearly superseded.\n- Record only reusable project knowledge: architecture and ownership, confirmed conventions, important invariants, validated commands, and unresolved follow-up that future work needs to know.\n- Clearly label unresolved or unverified details. Do not turn assumptions into facts.\n- Never record secrets, credentials, tokens, personal data, or sensitive values. Do not copy large code blocks or routine chat summaries into the knowledge file.\n- Do not modify application code, configuration, migrations, or other documentation as part of this task.\n\n## Update Process\n1. Identify candidate facts from the conversation, including what changed and what was verified.\n2. Check existing knowledge and relevant files for accuracy, relevance, and duplication.\n3. Make the smallest useful edit to `PROJECT_KNOWLEDGE.md`, preserving valid existing information and its style.\n4. If the chat produced no durable knowledge, leave the file unchanged and say so.\n5. Report the knowledge topics added, changed, or left unchanged, and note any uncertainty.", "variables": [], "notes": "Summarize durable, verified project knowledge from this chat and update the repository knowledge Markdown file. Run at the end of a chat or implementation task. Tools: read, search, edit. Arguments: Optional focus area or files to prioritize.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/LocNguyen2000/monorepo-microservice", "path": ".github/prompts/update-project-knowledge.prompt.md", "ref": "0e97aa30d28732329d6efaf68357abbdfb97c77b", "url": "https://github.com/LocNguyen2000/monorepo-microservice/blob/0e97aa30d28732329d6efaf68357abbdfb97c77b/.github/prompts/update-project-knowledge.prompt.md", "key": "LocNguyen2000/monorepo-microservice/.github/prompts/update-project-knowledge.prompt.md" } } }

Update Project Knowledge

About

Source and Scope

Update Process

Use it

Install Update Project Knowledge 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