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 file imported from nightgauge/nightgauge (.codex/prompts/nightgauge-feature-validate.md). Fill in {{arguments}} before use. Copyright stays with the author.
Run the Nightgauge Codex adapter wrapper for feature validation.
If no issue number is provided, ask for one.
Run scripts/run-stage.sh codex feature-validate {{arguments}}.
Summarize the result and suggest the next stage command.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Run the Nightgauge Codex adapter wrapper for feature validation.
1. If no issue number is provided, ask for one.
2. Run `scripts/run-stage.sh codex feature-validate {{arguments}}`.
3. Summarize the result and suggest the next stage command.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Run the Nightgauge Codex adapter wrapper for feature validation.\n\n1. If no issue number is provided, ask for one.\n2. Run `scripts/run-stage.sh codex feature-validate {{arguments}}`.\n3. Summarize the result and suggest the next stage command.",
"variables": [
"arguments"
],
"notes": "Run Nightgauge validation stage for an issue. Arguments: <issue-number> [extra stage args].",
"metadata": {
"source": {
"provider": "github-codex-prompts",
"repository": "https://github.com/nightgauge/nightgauge",
"path": ".codex/prompts/nightgauge-feature-validate.md",
"ref": "d2859391123840eefd4c55c231d9b87370ef29fd",
"url": "https://github.com/nightgauge/nightgauge/blob/d2859391123840eefd4c55c231d9b87370ef29fd/.codex/prompts/nightgauge-feature-validate.md",
"key": "nightgauge/nightgauge/.codex/prompts/nightgauge-feature-validate.md"
}
}
}
Installed into a catalogue, chosen by a router
Install nightgauge-feature-validate 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.