How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

clude - Skill - OpenSmartRoute

Imported from sebbsssss/clude (AGENTS.md). Install upstream with npx skills add sebbsssss/clude. Copyright stays with the author.

Clude Bot

gstack

Use the /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.

Available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /investigate, /document-release, /codex, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade.

Clude Memory (Required for ALL agents)

Clude is our product. Every agent MUST actively use it. The clude-memory MCP server is configured in .mcp.json.

Every heartbeat / conversation, you MUST:

Store memories about your work: decisions made, findings, blockers, task outcomes, things learned. Use store_memory with source: "mcp:<your-role>" (e.g. mcp:ceo, mcp:lead-pm, mcp:researcher).
Recall memories when starting work on a topic you may have context on. Use recall_memories before diving in.
Minimum 1 memory per heartbeat where you do meaningful work. More is better.

Memory type guide:

episodic — events, task completions, meetings, incidents
semantic — facts, knowledge, architecture decisions, team info
procedural — how-to knowledge, workflows, patterns that work
self_model — reflections on your own performance, strengths, gaps

Always include: meaningful tags, importance (0-1), and summary. This is our product — dogfood it seriously.

Staging Workflow (Required)

All changes go through staging first. See CLAUDE.md for the full workflow.

Key rules for all agents:

All PRs target staging, never main
No direct pushes to main or staging
Board verifies at cludebot-test-preview.up.railway.app before approving merge to main
When shipping, always set base branch to staging

Install clude 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.

clude

About

Clude Bot

gstack

Clude Memory (Required for ALL agents)

Staging Workflow (Required)

Install clude and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews