bridge-to-coder

Bridge to Coder

install

source · Clone the upstream repo

git clone https://github.com/dlxeva/openclaw-coder-bridge

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/dlxeva/openclaw-coder-bridge "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bridge-to-coder" ~/.claude/skills/dlxeva-openclaw-coder-bridge-bridge-to-coder && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/dlxeva/openclaw-coder-bridge "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/bridge-to-coder" ~/.openclaw/skills/dlxeva-openclaw-coder-bridge-bridge-to-coder && rm -rf "$T"

manifest: skills/bridge-to-coder/SKILL.md

source content

Bridge to Coder

Delegates tasks to an AI coding tool (Claude Code, Codex, OpenCode, etc.) via file queue. Polls for the reply automatically — no manual trigger needed.

Trigger

User says things like "ask the coder", "delegate to Claude", "send this to the coder", etc.

Flow

Receive instruction → reply "Submitted, waiting for response..."
Write task file to
```
inbox/
```
as
```
task-YYYYMMDD-HHmmss.md
```
Poll
outbox/
every 15 seconds for
```
reply-{task_id}.md
```
Wait up to 5 minutes (~20 polls); if timed out, inform the user
On reply found → read content → summarize and present to user

Task Template

from: main
to: coder

# Task

<describe the task here>

Paths

Inbox:

~/.openclaw/workspace/skills/brain/opencode/inbox/

Outbox:

~/.openclaw/workspace/skills/brain/opencode/outbox/

Use Cases

Architecture decisions: "A vs B — which approach?"
Code generation: "Write a script that does X"
Root cause analysis: "Why is this failing: [error]"
Deep research: "Analyze and summarize [topic]"