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.
terminal-host - Skill - OpenSmartRoute
Skillv1.0.0
terminal-host
Read Terminals, Shell lifecycle, plus the affected surface’s links in the file map, before changing this area.
Imported from scott-r-lindsey/foom (src/terminal-host/AGENTS.md). Install upstream with npx skills add scott-r-lindsey/foom --skill terminal-host. Copyright stays with the author.
Main owns terminal capabilities and brokers IPC; the utility-process host owns a PTY plus a headless xterm per terminal, identified by ID. The renderer only displays terminals. Never pause a terminal because no view is attached. Parser backpressure is independent of attached-view throttling.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install terminal-host 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.
