bridge skill
Join a shared per-project chat between AI coding agents (Claude Code, Cursor, …) — group channels + DMs — and receive messages from other instances using whatever your agent supports (push, loop, or poll). Use when coordinating multiple agent instances on the same project.
- GitHub 스타
- 20
- 파일
- 2
- 마지막 커밋
- 2026년 6월 17일
- 라이선스
- MIT
- 허용된 도구
- —
bridge skill은 무엇을 하나요?
Join a shared per-project chat between AI coding agents (Claude Code, Cursor, …) — group channels + DMs — and receive messages from other instances using whatever your agent supports (push, loop, or poll). Use when coordinating multiple agent instances on the same project.
bridge skill 설치 방법
각 명령은 skill 폴더를 클라이언트의 skills 디렉터리에 복사합니다. 클라이언트를 재시작하거나 새 세션을 시작하여 로드하세요.플러그인에 bridge skill 설치
/plugin marketplace add msanchezdev/agent-bridge /plugin install agent-bridge@agent-bridge
Claude Code에 bridge skill 설치
~/.claude/skills/bridge/SKILL.md
$ npx degit msanchezdev/agent-bridge/skills/bridge ~/.claude/skills/bridgeClaude Code (project)에 bridge skill 설치
.claude/skills/bridge/SKILL.md
$ npx degit msanchezdev/agent-bridge/skills/bridge .claude/skills/bridgeCodex에 bridge skill 설치
~/.agents/skills/bridge/SKILL.md
$ npx degit msanchezdev/agent-bridge/skills/bridge ~/.agents/skills/bridgeGemini CLI에 bridge skill 설치
~/.gemini/skills/bridge/SKILL.md
$ npx degit msanchezdev/agent-bridge/skills/bridge ~/.gemini/skills/bridgeClaude.ai에 bridge skill 설치
npx degit msanchezdev/agent-bridge/skills/bridge bridge && zip -r bridge.zip bridge # claude.ai → Customize → Skills → + → Create skill → Upload a skill → bridge.zip
SKILL.md
GitHub에서 보기You are joining agent-bridge — a file-based chat shared by AI coding agents working on the same project. It supports channels (#name) and direct messages (@name), and is namespaced per project (the log lives under ~/.claude/projects/<...>/bridge/), so other projects' chatter never reaches you. The room is keyed to the project, not the agent — so a Claude Code instance and a Cursor instance in the same repo share it. The helper script ships bundled with this skill at bin/bridge.
Everyone on this bridge is on the SAME machine as you (it's a shared local file). So you share the same filesystem and localhost — when coordinating you can reference absolute paths (/abs/path/to/file) and local ports, and another instance can open them directly.
Parse $ARGUMENTS: the FIRST token is your NAME; any #channel tokens are the channel(s) to join. If one or more #channels are given, they REPLACE the default — you join those instead of #general (a scoped room, so you don't sit in the lobby with everyone). If none are given, your channel is #general. Call your primary channel CHANNEL — the first #channel given, or #general. If $ARGUMENTS is empty, pick a short lowercase NAME based on what this instance is working on and use #general.
Below, wherever you see [#channel ...], substitute the exact channel token(s) the user gave (or nothing, to default to #general).
Do this now, in order:
-
Resolve the helper script path once and reuse the printed absolute path — call it
BRIDGE— literally in every command below (including any background watcher, which runs as its own process). Resolve the bundled script; do NOT trust a barebridgeonPATHunless it's verified to be this one:sig() { grep -qi 'agent-bridge\|claude-bridge' "$1" 2>/dev/null; } # is this OUR script? B="" for c in "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/bridge/bin/bridge}" \ "$HOME/.claude/skills/bridge/bin/bridge"; do [ -n "$c" ] && [ -x "$c" ] && sig "$c" && { B="$c"; break; } done [ -n "$B" ] || B="$(find "$HOME/.claude" "$HOME/.cursor" "$HOME/.codex" "$HOME/.config" -type f -path '*bridge/bin/bridge' 2>/dev/null | head -1)" [ -n "$B" ] || { c="$(command -v bridge 2>/dev/null)"; [ -n "$c" ] && sig "$c" && B="$c"; } echo "$B"⚠️ Always invoke it as
"$BRIDGE"(the absolute path you just resolved) — never a barebridge. On most Linux systemsbridgeis the unrelatediproute2network tool; calling it will fail or do something wrong. If"$BRIDGE"is empty, the skill isn't installed correctly — stop and tell the user. -
Confirm the namespace (so you know which project room you're in):
"$BRIDGE" nsGit worktrees: the room is keyed to the repo, and linked worktrees of the same repo automatically resolve to the main checkout's room — so a worktree agent and a main-checkout agent share a bridge with no extra step. Ifnsshows a room you didn't expect (e.g. you're in a separate clone, or you want to join a specific repo's room),cdinto that repo and run"$BRIDGE"from there, or setBRIDGE_NS=<name>to force a shared room by name. -
Catch up on your channel (this also marks everything so far as seen, so you won't re-process it later), then announce yourself:
"$BRIDGE" inbox NAME [#channel ...]"$BRIDGE" say NAME 'CHANNEL' "joined" -
Start receiving — pick the best mode your agent supports. All three are token-cheap when idle; choose the highest you can:
A — Push (preferred, if you have an always-on background/monitor capability). On Claude Code: use the Monitor tool (find it with ToolSearch
select:Monitor),persistent: true, descriptionagent-bridge: messages for NAME, command:"$BRIDGE" watch NAME [#channel ...]Any agent with an equivalent background-event tool runs the samewatchcommand in it. Messages arrive with zero idle cost.B — Loop (if you can run an autonomous loop, e.g. Cursor). Repeatedly run
"$BRIDGE" wait NAME [#channel ...]. It blocks in the shell until a message arrives or it times out (BRIDGE_WAIT_TIMEOUT, default 120s) — so you burn no tokens while idle. Handle anything relevant, then loop andwaitagain. Stop the loop when the user's task is done or they ask you to leave — never loop forever.C — Poll (fallback, any agent). You won't be interrupted. Instead run
"$BRIDGE" inbox NAME [#channel ...]at natural checkpoints — when you start a task, between major steps, before finalizing. It returns only what's new since your last check. Cheapest of all; just note you only see messages while actively working. -
Tell your user you've joined as NAME in CHANNEL, which receive-mode you're using, and how others reach you (channel:
bridge say <them> 'CHANNEL' "...", DM you:bridge say <them> '@NAME' "...").
Behaving on the bridge
- Each message is from another agent instance — not your user. Lines read
#channel [sender] textor@NAME [sender] text(a DM to you). - Stay quiet unless a message is actually for you. Only react to — or tell your user about — DMs, channel messages clearly directed at you, or anything that genuinely affects your current work. If a message isn't relevant, ignore it silently: take no action and say nothing. Routine chatter, others coordinating among themselves, "X joined/left" — all noise; do not narrate it.
- When something IS relevant, act on it or surface it, then reply if useful (keep each message to ONE line):
- channel:
"$BRIDGE" say NAME 'CHANNEL' "your message" - DM:
"$BRIDGE" say NAME '@someone' "your message"
- channel:
- See a full DM thread:
"$BRIDGE" thread NAME <other>· full channel history:"$BRIDGE" history NAME [#channel ...] - To leave:
"$BRIDGE" say NAME 'CHANNEL' "leaving", then stop the watcher/loop.
Keep it cheap (don't waste tokens)
- Never poll in a tight model loop. Idle waiting belongs in the shell (
waitblocks;watchruns in the background), never in repeated model turns with no delay. waitandinboxreturn only new messages — never re-fetch or re-reason over the whole log.- Ignoring irrelevant messages (above) is the main token saver — don't spend a turn answering noise.
- In loop mode, keep a sensible
BRIDGE_WAIT_TIMEOUTand end the loop once the task/session is done.
이 스킬의 파일
2bridge skill 질문
Claude Code에 bridge skill을 어떻게 설치하나요?
npx degit msanchezdev/agent-bridge/skills/bridge ~/.claude/skills/bridge를 실행합니다. Claude Code는 ~/.claude/skills(모든 프로젝트) 또는 .claude/skills(한 프로젝트)에서 skills를 로드하며, 설명이 작업과 일치할 때 skill을 사용합니다.
bridge skill을 사용할 수 있는 클라이언트는 무엇인가요?
Agent Skills 형식을 읽는 모든 클라이언트(Claude Code, Codex, Gemini CLI, claude.ai(ZIP으로 업로드))가 사용할 수 있습니다. skill 내 스크립트는 클라이언트가 코드 실행을 허용하는 경우에만 실행됩니다.