Client setup references

Integrations

Draft field maps, config blocks and troubleshooting notes. Each guide stays marked pending until its recorded compatibility fixture passes.

Base URLhttps://api.minirouter.sh/v1

Get a keyhttps://minirouter.sh/key

Clients

Agent setup target →

Coding agents and editors

Driven by a person, task by task. Bursty, interrupted often, and stopped by hand.

ClientCline
SurfaceVS Code extension
Fixture suitePENDING
→
ClientRoo Code
SurfaceVS Code extension
Fixture suitePENDING
→
ClientKilo Code
SurfaceVS Code extension
Fixture suitePENDING
→
ClientOpenCode
SurfaceTerminal agent
Fixture suitePENDING
→
ClientContinue
SurfaceVS Code / JetBrains extension
Fixture suitePENDING
→
ClientAider
SurfaceTerminal pair programmer
Fixture suitePENDING
→
ClientZed
SurfaceEditor
Fixture suitePENDING
→

Always-on personal agents

Personal agents →

Spend unattended, re-send a long prefix every turn, and need a cap more than they need capability.

ClientOpenClaw
SurfaceAlways-on personal agent
Fixture suitePENDING
→
ClientHermes Agent
SurfaceAlways-on personal agent
Fixture suitePENDING
→
ClientOpenHands
SurfaceAutonomous coding agent
Fixture suitePENDING
→

Roleplay frontends

Roleplay clients →

A long static prefix against a short reply, regenerated constantly, with nothing stored on our side.

ClientSillyTavern
SurfaceRoleplay frontend
Fixture suitePENDING
→
ClientRisuAI
SurfaceRoleplay frontend
Fixture suitePENDING
→
ClientAgnai
SurfaceRoleplay frontend
Fixture suitePENDING
→

Verified means a captured real request, including a tool-calling turn and an aborted stream, replayed green in CI. Pending means the guide is a draft: compatibility has not been confirmed yet.