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.
handoff - Prompt - OpenSmartRoute
Promptv1.0.0
handoff
Execute Handoff using docs/architecture/agent-workflow.md. Publish branch/HEAD, verified work, failures, uncommitted files, blockers and exact next action on the issue.
Prompt file imported from KanujVerma/drift (.cursor/commands/handoff.md). Copyright stays with the author.
Execute Handoff using docs/architecture/agent-workflow.md. Publish branch/HEAD, verified work, failures, uncommitted files, blockers and exact next action on the issue. Record explicit writer release if transferring work. Do not modify another worktree or create a duplicate status document.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Execute Handoff using docs/architecture/agent-workflow.md. Publish branch/HEAD, verified work, failures, uncommitted files, blockers and exact next action on the issue. Record explicit writer release if transferring work. Do not modify another worktree or create a duplicate status document.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Execute Handoff using docs/architecture/agent-workflow.md. Publish branch/HEAD, verified work, failures, uncommitted files, blockers and exact next action on the issue. Record explicit writer release if transferring work. Do not modify another worktree or create a duplicate status document.",
"variables": [],
"notes": "Execute Handoff using docs/architecture/agent-workflow.md. Publish branch/HEAD, verified work, failures, uncommitted files, blockers and exact next action on the issue. Record explicit writer release if transferring work. Do not modify another worktree or create a duplicate status document.",
"metadata": {
"source": {
"provider": "github-cursor-commands",
"repository": "https://github.com/KanujVerma/drift",
"path": ".cursor/commands/handoff.md",
"ref": "e97d0276283e28235f638c705117888e82e1f2bc",
"url": "https://github.com/KanujVerma/drift/blob/e97d0276283e28235f638c705117888e82e1f2bc/.cursor/commands/handoff.md",
"key": "KanujVerma/drift/.cursor/commands/handoff.md"
}
}
}
Installed into a catalogue, chosen by a router
Install handoff 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.