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.

relay - Prompt - OpenSmartRoute

Name: relay
Author: UNIL-DESI

Prompt file imported from UNIL-DESI/aivc (.cursor/commands/relay.md). Copyright stays with the author.

Relay — Transition Maestro

This command performs a clean shutdown of the current Maestro session and prepares a handover for the next one.

Procedure (execute in this exact order)

Step 1: Stop All Sub-Agents

manage_subagents → list to identify all active sub-agents.
For each active sub-agent:
- Send a send_message asking for a final status report (what was done, what's pending, any partial results).
- Wait briefly for responses (set a schedule(DurationSeconds=60) timer).
After collecting reports (or timeout): manage_subagents → kill_all.
No zombie agents must survive this step.

Step 2: Finalize the Archive

Move any remaining content from updates.md into walkthrough.md.
Add a closing section to walkthrough.md:

---

## 🏁 Session Close — [date]

**Reason**: Relay to new Maestro session.

### Final State of In-Progress Tasks
| Issue | Status at close | Partial results | Next steps |
|-------|----------------|-----------------|------------|
| #XX   | ...            | ...             | ...        |

### Unresolved Questions
- [Any questions that were pending in updates.md]

### AIVC Memory
- [Confirm all key decisions were committed to memory]

Clear updates.md — overwrite with:

# Updates

> Session closed via /relay. See walkthrough.md for the full archive.
> A new Maestro session will pick up from here.

Step 3: Commit to AIVC Memory

remember a detailed note including:

Summary of what was accomplished this session.
State of all open issues (which are done, which are in progress, which are blocked).
Key decisions taken.
Path to the walkthrough artifact for reference.

Step 4: Generate the Relay Prompt

Output a relay prompt that the user can paste into a new conversation. Format:

/maestro

## Relay from previous session

**Previous walkthrough**: [absolute path to walkthrough.md]
**Previous updates**: [absolute path to updates.md]
**Conversation ID**: [current conversation ID]

### Context
[2-3 sentence summary of what the project is about and where we are]

### Open Issues (carry over)
| Issue | Priority | Status | Notes |
|-------|----------|--------|-------|
| #XX   | ...      | ...    | ...   |

### Key Decisions from Previous Session
- [Decision 1]
- [Decision 2]

### Immediate Next Steps
1. [What the next Maestro should do first]
2. [Second priority]

Step 5: Confirm

Tell the user (in the chat AND in updates.md) that the relay is ready:

All agents stopped.
Archive finalized.
Memory committed.
Relay prompt generated — ready to paste into a new conversation.

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

# Relay — Transition Maestro This command performs a **clean shutdown** of the current Maestro session and prepares a handover for the next one. --- ## Procedure (execute in this exact order) ### Step 1: Stop All Sub-Agents 1. `manage_subagents` → `list` to identify all active sub-agents. 2. For each active sub-agent: - Send a `send_message` asking for a **final status report** (what was done, what's pending, any partial results). - Wait briefly for responses (set a `schedule(DurationSeconds=60)` timer). 3. After collecting reports (or timeout): `manage_subagents` → `kill_all`. 4. No zombie agents must survive this step. ### Step 2: Finalize the Archive 1. Move any remaining content from `updates.md` into `walkthrough.md`. 2. Add a **closing section** to `walkthrough.md`: ```markdown --- ## 🏁 Session Close — [date] **Reason**: Relay to new Maestro session. ### Final State of In-Progress Tasks | Issue | Status at close | Partial results | Next steps | |-------|----------------|-----------------|------------| | #XX | ... | ... | ... | ### Unresolved Questions - [Any questions that were pending in updates.md] ### AIVC Memory - [Confirm all key decisions were committed to memory] ``` 3. Clear `updates.md` — overwrite with: ```markdown # Updates > Session closed via /relay. See walkthrough.md for the full archive. > A new Maestro session will pick up from here. ``` ### Step 3: Commit to AIVC Memory `remember` a detailed note including: - Summary of what was accomplished this session. - State of all open issues (which are done, which are in progress, which are blocked). - Key decisions taken. - Path to the walkthrough artifact for reference. ### Step 4: Generate the Relay Prompt Output a **relay prompt** that the user can paste into a new conversation. Format: ```markdown /maestro ## Relay from previous session **Previous walkthrough**: [absolute path to walkthrough.md] **Previous updates**: [absolute path to updates.md] **Conversation ID**: [current conversation ID] ### Context [2-3 sentence summary of what the project is about and where we are] ### Open Issues (carry over) | Issue | Priority | Status | Notes | |-------|----------|--------|-------| | #XX | ... | ... | ... | ### Key Decisions from Previous Session - [Decision 1] - [Decision 2] ### Immediate Next Steps 1. [What the next Maestro should do first] 2. [Second priority] ``` ### Step 5: Confirm Tell the user (in the chat AND in updates.md) that the relay is ready: - All agents stopped. - Archive finalized. - Memory committed. - Relay prompt generated — ready to paste into a new conversation.

{ "prompt": "# Relay — Transition Maestro\n\nThis command performs a **clean shutdown** of the current Maestro session and prepares a handover for the next one.\n\n---\n\n## Procedure (execute in this exact order)\n\n### Step 1: Stop All Sub-Agents\n\n1. `manage_subagents` → `list` to identify all active sub-agents.\n2. For each active sub-agent:\n - Send a `send_message` asking for a **final status report** (what was done, what's pending, any partial results).\n - Wait briefly for responses (set a `schedule(DurationSeconds=60)` timer).\n3. After collecting reports (or timeout): `manage_subagents` → `kill_all`.\n4. No zombie agents must survive this step.\n\n### Step 2: Finalize the Archive\n\n1. Move any remaining content from `updates.md` into `walkthrough.md`.\n2. Add a **closing section** to `walkthrough.md`:\n\n```markdown\n---\n\n## 🏁 Session Close — [date]\n\n**Reason**: Relay to new Maestro session.\n\n### Final State of In-Progress Tasks\n| Issue | Status at close | Partial results | Next steps |\n|-------|----------------|-----------------|------------|\n| #XX | ... | ... | ... |\n\n### Unresolved Questions\n- [Any questions that were pending in updates.md]\n\n### AIVC Memory\n- [Confirm all key decisions were committed to memory]\n```\n\n3. Clear `updates.md` — overwrite with:\n```markdown\n# Updates\n\n> Session closed via /relay. See walkthrough.md for the full archive.\n> A new Maestro session will pick up from here.\n```\n\n### Step 3: Commit to AIVC Memory\n\n`remember` a detailed note including:\n- Summary of what was accomplished this session.\n- State of all open issues (which are done, which are in progress, which are blocked).\n- Key decisions taken.\n- Path to the walkthrough artifact for reference.\n\n### Step 4: Generate the Relay Prompt\n\nOutput a **relay prompt** that the user can paste into a new conversation. Format:\n\n```markdown\n/maestro\n\n## Relay from previous session\n\n**Previous walkthrough**: [absolute path to walkthrough.md]\n**Previous updates**: [absolute path to updates.md]\n**Conversation ID**: [current conversation ID]\n\n### Context\n[2-3 sentence summary of what the project is about and where we are]\n\n### Open Issues (carry over)\n| Issue | Priority | Status | Notes |\n|-------|----------|--------|-------|\n| #XX | ... | ... | ... |\n\n### Key Decisions from Previous Session\n- [Decision 1]\n- [Decision 2]\n\n### Immediate Next Steps\n1. [What the next Maestro should do first]\n2. [Second priority]\n```\n\n### Step 5: Confirm\n\nTell the user (in the chat AND in updates.md) that the relay is ready:\n- All agents stopped.\n- Archive finalized.\n- Memory committed.\n- Relay prompt generated — ready to paste into a new conversation.", "variables": [], "notes": "Clôture propre d'une session Maestro — arrête les agents, archive les résultats, prépare la relève.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/UNIL-DESI/aivc", "path": ".cursor/commands/relay.md", "ref": "8b07e2b644f81e0de936250d5c52bc90a1f43791", "url": "https://github.com/UNIL-DESI/aivc/blob/8b07e2b644f81e0de936250d5c52bc90a1f43791/.cursor/commands/relay.md", "key": "UNIL-DESI/aivc/.cursor/commands/relay.md" } } }

relay

About

Relay — Transition Maestro

Procedure (execute in this exact order)

Step 1: Stop All Sub-Agents

Step 2: Finalize the Archive

Step 3: Commit to AIVC Memory

Step 4: Generate the Relay Prompt

Step 5: Confirm

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