Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
30-playback-pipeline - Prompt - OpenSmartRoute
Promptv1.0.0
30-playback-pipeline
Goal: After source plugins are stable, implement: - episode -> server links - resolver selection - playback session creation - player handoff
Prompt file imported from Brizhelito/kumoriya (.codex/prompts/30-playback-pipeline.md). Copyright stays with the author.
Codex Prompt - Playback Pipeline
Goal:
After source plugins are stable, implement:
episode -> server links
resolver selection
playback session creation
player handoff
Constraints:
WebView remains last-resort infrastructure
do not mix resolver logic into UI or player widgets
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# Codex Prompt - Playback Pipeline
Goal:
After source plugins are stable, implement:
- episode -> server links
- resolver selection
- playback session creation
- player handoff
Constraints:
- WebView remains last-resort infrastructure
- do not mix resolver logic into UI or player widgets
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "# Codex Prompt - Playback Pipeline\n\nGoal:\nAfter source plugins are stable, implement:\n- episode -> server links\n- resolver selection\n- playback session creation\n- player handoff\n\nConstraints:\n- WebView remains last-resort infrastructure\n- do not mix resolver logic into UI or player widgets",
"variables": [],
"notes": "Goal: After source plugins are stable, implement: - episode -> server links - resolver selection - playback session creation - player handoff",
"metadata": {
"source": {
"provider": "github-codex-prompts",
"repository": "https://github.com/Brizhelito/kumoriya",
"path": ".codex/prompts/30-playback-pipeline.md",
"ref": "60d65a7e00d1dd6e989b224d4b6953c80e1f85cf",
"url": "https://github.com/Brizhelito/kumoriya/blob/60d65a7e00d1dd6e989b224d4b6953c80e1f85cf/.codex/prompts/30-playback-pipeline.md",
"key": "Brizhelito/kumoriya/.codex/prompts/30-playback-pipeline.md"
}
}
}
Installed into a catalogue, chosen by a router
Install 30-playback-pipeline 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.