Menu
Operator-facing guide for the redis-channel Claude Code channel plugin. Use when the user wants to connect a Claude Code session to an external router over Redis Streams, list registered sessions, change endpoints, or troubleshoot the bridge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Route proposed Team Mimir profile behavior changes to target-owned Hermes dialogue.
Build a versioned Antigravity teammate delegation envelope and route it through the guarded agy wrapper.
Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "break this down", or a handoff issue ready for planning.
Coordinate a whole outcome as a durable DAG of leaf sagas. A level-triggered reconcile loop that dispatches the ready frontier to executors, harvests completion, and pages the operator only at gates and exceptions. The coordinator routes and never runs leaf work; status is derived on read. Thin coordinator verbs only — start, graph, advance, attend, resume, discover, handoff, attach — leaf work stays the native /resume, /work, /code-review, /qa.
Execute a settled Infiquetra plan to PR-ready, then own the round-N PR continuation loop. Restores and writes the work-thread saga (the primary writer), recommends an execution backend, runs risk-gated tests, calls /code-review programmatically and reads its envelope, gates hard on P0/P1 and stale reviews, and coordinates PR-open/review-request/merge under explicit confirmation — without owning deploy. Triggers on "build it", "work this plan", "execute the plan", "resume work on
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.
| name | redis-channel |
| description | Operator-facing guide for the redis-channel Claude Code channel plugin. Use when the user wants to connect a Claude Code session to an external router over Redis Streams, list registered sessions, change endpoints, or troubleshoot the bridge. |
redis-channel is a Claude Code channel that runs as an MCP subprocess of your session. It speaks a Redis-streams protocol (see PROTOCOL.md) and bridges to any consumer on the other side — any router that implements the protocol can drive it. One reference consumer is hermes-claude-code-router for Discord/voice hands-free workflows.
| Command | Effect |
|---|---|
/redis-channel connect [<endpoint>] | Register session presence with the named Redis endpoint (default: registry's default_endpoint, falls back to the sole configured endpoint when only one exists). |
/redis-channel disconnect | Cleanly remove session from registry; stop consuming streams. |
/redis-channel list | Show configured endpoints + current connection status. |
/redis-channel rename <name> | Change the session's name in the registry (must be unique). |
/redis-channel configure <endpoint> | Add or update an endpoint in the local registry. |
/redis-channel mode <auto|always_route|never_route> | Override the router-side routing default for this session. |
~/.claude/channels/redis-channel/registry.json lists known endpoints. Example:
{
"endpoints": {
"default": {
"redis_url": "redis://redis-host.example.com:6379/0",
"redis_password_env": "MY_REDIS_PASSWORD",
"display_name": "Default router endpoint"
}
},
"defaults": {
"session_name_override_env": "CLAUDE_SESSION_NAME",
"heartbeat_seconds": 10,
"registry_ttl_seconds": 60,
"destructive_confirm_seconds": 3,
"permission_window_seconds": 30,
"consumer_block_ms": 1000,
"default_endpoint": "default",
"auto_connect_endpoint": null
}
}
The password lives in an env var (referenced by redis_password_env); never commit secrets to disk. The env var is populated by ~/.claude/channels/redis-channel/source-env.sh — see docs/source-env.example.sh in the plugin for a template.
| Symptom | Likely cause | Fix |
|---|---|---|
connect fails: NOAUTH | env var named in redis_password_env is unset | edit ~/.claude/channels/redis-channel/source-env.sh to export it |
connect fails: Connection refused | Redis unreachable or wrong URL | verify with redis-cli -h <host> -p <port> ping |
Session not appearing in router's list sessions | Heartbeat key missing | check CC plugin process is running; cc-sessions:hb:<name> exists in Redis |
| Replies don't reach Discord/etc | Router not consuming outbound | check router-side consumer-group status: XINFO GROUPS cc-sessions:<name>:outbound |
| Permission prompt fires but no reply heard back | Voice STT didn't match "yes/no " | check router-side audit log; verify confidence threshold |
PROTOCOL.md — wire format (CC ↔ router)docs/STATE_MACHINE.md — routing-target state machine (router-side)agents/redis-channel-coach.md — Claude behavior hints when this channel is active