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.

handoff - Prompt - OpenSmartRoute

Name: handoff
Author: homeofe

Prompt file imported from homeofe/aahp-runner (.claude/commands/handoff.md). Copyright stays with the author.

Perform a complete AAHP v3 handoff for the current session. Follow these steps exactly:

Step 1: Create Lock

Create .ai/handoff/HANDOFF.lock with current agent identity and timestamp.

Step 2: Update STATUS.md

Rewrite .ai/handoff/STATUS.md to reflect the CURRENT state of the project. Include:

Build health (build, test, lint, type-check results)
Infrastructure state
Services/components status
What is missing
Recently resolved items
Trust levels for all claims

Step 3: Update NEXT_ACTIONS.md

Mark completed tasks as done (move to "Recently Completed")
Add any newly discovered tasks
Ensure max 5 active (unblocked) tasks
Update blocked status for any blocked tasks

Step 4: Append to LOG.md

Add a session summary entry at the TOP of LOG.md:

## [DATE] Session: [Brief Title]

> **Agent:** [model name]
> **Timestamp:** [ISO-8601]

**What was done:**
- Bullet points of work completed

**Decisions made:**
- Any decisions or trade-offs

**Open items:**
- What remains to be done

If LOG.md exceeds 10 entries, move older entries to LOG-ARCHIVE.md.

Step 5: Update DASHBOARD.md

Update build status and test counts
Update pipeline state
Update open tasks table

Step 6: Regenerate MANIFEST.json

Compute SHA-256 checksums for ALL handoff files
Count lines in each file
Write one-line summaries
Update last_session metadata
Update quick_context (2-3 sentences)
Estimate token budgets
Preserve task graph data

Step 7: Remove Lock & Commit

Delete HANDOFF.lock
Stage all handoff files: git add .ai/handoff/
Commit: feat(handoff): session handoff [AAHP-auto]

Report the handoff summary to the user when complete.

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.

{ "prompt": "Perform a complete AAHP v3 handoff for the current session. Follow these steps exactly:\n\n## Step 1: Create Lock\nCreate `.ai/handoff/HANDOFF.lock` with current agent identity and timestamp.\n\n## Step 2: Update STATUS.md\nRewrite `.ai/handoff/STATUS.md` to reflect the CURRENT state of the project. Include:\n- Build health (build, test, lint, type-check results)\n- Infrastructure state\n- Services/components status\n- What is missing\n- Recently resolved items\n- Trust levels for all claims\n\n## Step 3: Update NEXT_ACTIONS.md\n- Mark completed tasks as done (move to \"Recently Completed\")\n- Add any newly discovered tasks\n- Ensure max 5 active (unblocked) tasks\n- Update blocked status for any blocked tasks\n\n## Step 4: Append to LOG.md\nAdd a session summary entry at the TOP of LOG.md:\n```\n## [DATE] Session: [Brief Title]\n\n> **Agent:** [model name]\n> **Timestamp:** [ISO-8601]\n\n**What was done:**\n- Bullet points of work completed\n\n**Decisions made:**\n- Any decisions or trade-offs\n\n**Open items:**\n- What remains to be done\n```\nIf LOG.md exceeds 10 entries, move older entries to LOG-ARCHIVE.md.\n\n## Step 5: Update DASHBOARD.md\n- Update build status and test counts\n- Update pipeline state\n- Update open tasks table\n\n## Step 6: Regenerate MANIFEST.json\n- Compute SHA-256 checksums for ALL handoff files\n- Count lines in each file\n- Write one-line summaries\n- Update last_session metadata\n- Update quick_context (2-3 sentences)\n- Estimate token budgets\n- Preserve task graph data\n\n## Step 7: Remove Lock & Commit\n- Delete HANDOFF.lock\n- Stage all handoff files: `git add .ai/handoff/`\n- Commit: `feat(handoff): session handoff [AAHP-auto]`\n\nReport the handoff summary to the user when complete.", "variables": [], "notes": "Complete AAHP handoff cycle: update state files, log session, regenerate manifest Tools: Read, Edit, Write, Bash(sha256sum*), Bash(wc*), Bash(date*), Bash(git*).", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/homeofe/aahp-runner", "path": ".claude/commands/handoff.md", "ref": "de2cac84744bf16a37d426fb4ec098f27f0361fe", "url": "https://github.com/homeofe/aahp-runner/blob/de2cac84744bf16a37d426fb4ec098f27f0361fe/.claude/commands/handoff.md", "key": "homeofe/aahp-runner/.claude/commands/handoff.md" } } }

handoff

About

Step 1: Create Lock

Step 2: Update STATUS.md

Step 3: Update NEXT_ACTIONS.md

Step 4: Append to LOG.md

Step 5: Update DASHBOARD.md

Step 6: Regenerate MANIFEST.json

Step 7: Remove Lock & Commit

Use it

Install handoff 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

Manifest

Reviews