Run standalone middleware gateway for Codex, Claude Code, OpenCode, and OpenClaw

Use this skill when you want an agent to install, start, verify, monitor, or wire up the standalone modeio-middleware runtime from https://github.com/mode-io/mode-io-middleware.

What this skill wraps

• Standalone product repo: https://github.com/mode-io/mode-io-middleware
• Product quickstart: https://github.com/mode-io/mode-io-middleware/blob/main/QUICKSTART.md
• Architecture: https://github.com/mode-io/mode-io-middleware/blob/main/ARCHITECTURE.md
• Plugin contract: https://github.com/mode-io/mode-io-middleware/blob/main/MODEIO_PLUGIN_PROTOCOL.md

Core routes

• POST /v1/chat/completions
• POST /v1/responses
• POST /connectors/claude/hooks
• GET /healthz
• GET /modeio/dashboard
• GET /modeio/api/events
• GET /modeio/api/events/{request_id}
• GET /modeio/api/stats
• GET /modeio/api/events/live

Recommended operator flow

1) Install the standalone runtime

From GitHub:

python -m pip install git+https://github.com/mode-io/mode-io-middleware

From a local checkout:

python -m pip install /path/to/mode-io-middleware

2) Start the gateway

export MODEIO_GATEWAY_UPSTREAM_API_KEY="<your-upstream-key>"

modeio-middleware-gateway \
  --host 127.0.0.1 \
  --port 8787 \
  --upstream-chat-url "https://api.openai.com/v1/chat/completions" \
  --upstream-responses-url "https://api.openai.com/v1/responses"

3) Route each supported client through middleware

modeio-middleware-setup --health-check

Codex CLI:

export OPENAI_BASE_URL="http://127.0.0.1:8787/v1"

OpenCode:

modeio-middleware-setup --apply-opencode --create-opencode-config

OpenClaw:

modeio-middleware-setup --apply-openclaw --create-openclaw-config

Claude Code:

modeio-middleware-setup --apply-claude --create-claude-settings

4) Validate health and monitoring

curl -s http://127.0.0.1:8787/healthz
open http://127.0.0.1:8787/modeio/dashboard
curl -s http://127.0.0.1:8787/modeio/api/events

5) Watch live traffic and request outcomes

• Open the built-in dashboard at http://127.0.0.1:8787/modeio/dashboard
• Use /modeio/api/events for recent requests, /modeio/api/stats for summary counters, and /modeio/api/events/live for SSE updates
• Use the standalone repo if you need to extend the dashboard implementation itself

6) Author or validate an external plugin

modeio-middleware-new-plugin my-policy
modeio-middleware-validate-plugin /path/to/manifest.json
modeio-middleware-plugin-conformance /path/to/manifest.json python3 /path/to/plugin.py

7) Roll back local routing

unset OPENAI_BASE_URL
modeio-middleware-setup --uninstall --apply-opencode --apply-openclaw --apply-claude

Behavior notes

• The standalone product repo is the runtime and packaging source of truth.
• This skill is intentionally thin: it gives agents reliable install/setup/health-check guidance instead of shipping the product implementation.
• The built-in dashboard, request journal, and monitoring APIs are runtime features owned by the standalone product repo; this wrapper should teach agents how to reach them.
• Public external plugins use stdio-jsonrpc; legacy_inprocess remains internal-only in the product repo.
• The bundled default config starts with no active plugins enabled.

When not to use

• You only need direct upstream API calls and do not want a local gateway process.
• You are editing the middleware product itself; use the standalone repo directly instead.
• You want to extend the dashboard, request journal, or browser monitoring UI itself; that belongs in the standalone product repo, not this wrapper.

References in this repo

• references/standalone-product.md — standalone repo handoff, install commands, and operator notes