Dai Ha
555715ced9
The repo moved lms/claude-bridge -> fleet/claude-bridge -> fleet/fleetd. Gitea redirects hold, so most of this is not urgent, but one line was a real break: the implementer skill posts a worker's PR to a hardcoded repo path, so every worker PR would have gone to the old address. .claude/skills/implementer/SKILL.md the worker PR endpoint (functional) .gitmodules wiki submodule URL CLAUDE.md + wiki/7-Use-Cases.md the canonical block, kept byte-identical README.md clone command and wiki link deploy/bridged.service Documentation= plugin/.claude-plugin/plugin.json homepage + repository docs/*.md issue and wiki links The wiki is not a separate repo. /repos/lms/claude-bridge.wiki returns 404 and lms owned no .wiki entity, so the wiki moved with the repo; both the old and the new wiki SSH URLs resolve to the same sha. Ticket step 4 assumed a second transfer that does not exist.
claude-bridge (Claude Code plugin)
Makes a project bridge-ready: mounts the bridged MCP gateway and applies standard Claude Code
settings, so the session can orchestrate a fleet of delegated workers.
This plugin ships no credentials. Every secret is referenced by environment-variable name; the values stay with the user. Nothing the plugin writes is unsafe to commit.
What it is not
The plugin is the client-side setup, not the bridge. bridged is a separate daemon and herdr
is a separate PTY multiplexer, each with its own lifecycle and install. The plugin mounts an
already-running daemon and tells you what is missing when one isn't there — it deliberately does
not try to install system services on your behalf.
Install
/plugin marketplace add ltms/claude-bridge
/plugin install claude-bridge@claude-bridge
Then, in the project you want to onboard:
/claude-bridge:setup
What you get
| Component | Effect |
|---|---|
.mcp.json |
mounts bridged at http://127.0.0.1:8765/mcp for any session with the plugin enabled |
skills/setup |
/claude-bridge:setup — preflight, project settings, credential guidance, and verification |
Because the plugin carries its own .mcp.json, an installed plugin needs no project-level MCP
file at all. The setup skill writes one only when you want the mount to work without the plugin —
for teammates who haven't installed it, or for CI.
Verifying a setup
The setup skill ends by requiring a real spawn, not a health check. /healthz only reports
that the daemon can reach herdr; a protocol mismatch between the daemon's adapter and the herdr
binary leaves health green while every spawn fails. Only a spawn that reaches ready proves the
fleet.
Local development
claude --plugin-dir ./plugin
claude plugin validate ./plugin
/reload-plugins picks up edits without restarting the session.