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.
{
"prompt": "<objective>\nScan `~/gsd-workspaces/` for workspace directories containing `WORKSPACE.md` manifests. Display a summary table with name, path, repo count, strategy, and GSD project status.\n</objective>\n\n<execution_context>\n@C:/Repo/blog_sertao/.claude/get-shit-done/workflows/list-workspaces.md\n@C:/Repo/blog_sertao/.claude/get-shit-done/references/ui-brand.md\n</execution_context>\n\n<process>\nExecute the list-workspaces workflow from @C:/Repo/blog_sertao/.claude/get-shit-done/workflows/list-workspaces.md end-to-end.\n</process>",
"variables": [],
"notes": "List active GSD workspaces and their status Tools: Bash, Read.",
"metadata": {
"source": {
"provider": "github-claude-commands",
"repository": "https://github.com/sertaoseracloud/sertao",
"path": ".claude/commands/gsd/list-workspaces.md",
"ref": "b33314eae57d2f3ca99cb08e89dc56cfad071fbb",
"url": "https://github.com/sertaoseracloud/sertao/blob/b33314eae57d2f3ca99cb08e89dc56cfad071fbb/.claude/commands/gsd/list-workspaces.md",
"key": "sertaoseracloud/sertao/.claude/commands/gsd/list-workspaces.md"
}
}
}
Installed into a catalogue, chosen by a router
Install gsd:list-workspaces 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.