协同代码桥

Install — two pastes total

Step 1 — on your machine (once). Open Terminal (Cmd + Space → Terminal), paste this, press Enter:

```bash

Verify your install

Run this any time to confirm the bridge is healthy:

cowork-to-code-bridge-selfcheck

It checks six things and prints a clear PASS/FAIL for each:

cowork-to-code-bridge selfcheck
  bridge root : /Users/you/.cowork-to-code-bridge
  platform    : Darwin arm64

  Bridge root        [PASS]  /Users/you/.cowork-to-code-bridge
  Bridge token       [PASS]  set in /Users/you/.cowork-to-code-bridge/.env
  Daemon registered  [PASS]  launchd: running (pid 1234)
  Skill installed    [PASS]  /Users/you/.claude/skills/cowork-to-code-bridge
  Ping round-trip    [PASS]  ping round-trip OK
  claude CLI         [PASS]  /opt/homebrew/bin/claude

  All checks passed. Bridge is healthy.

Exits 0 if all pass, 1 if any fail — safe to use in scripts or bug reports.

---

Uninstall

One command, undoes everything the installer did:

cowork-to-code-bridge-uninstall

It undoes everything the installer set up: stops and removes the background daemon, removes the global Cowork skill (so it stops loading into your Cowork sessions), deletes the bridge folder (token, scripts, history), and uninstalls the Python package. It asks before each destructive step — say yes to all to fully reset.

No network needed, no Cowork step. Uninstall is entirely on your Mac. Once the skill is removed, your Cowork chats simply won't have the bridge anymore — nothing to clean up there.

For a no-questions-asked uninstall:

cowork-to-code-bridge-uninstall --yes

Uninstall options

"I ran the installer but it said Python is too old."

Stock macOS ships an old Python (3.8). You need 3.10+. Easiest fix:

brew install python@3.12

Then re-run the installer.

"How do I know if my Mac is at clean uninstalled state?"

After running uninstall, all of these should return empty or "not found":

launchctl list | grep cowork-to-code-bridge
ls ~/Library/LaunchAgents/dev.cowork-to-code-bridge.daemon.plist
ls ~/.cowork-to-code-bridge
python3 -c "import cowork_to_code_bridge"

---

What you can build with it

Once the bridge is in place, a single Cowork chat can run a whole project — not just edit files, but actually run, test, and ship them. Paired with Claude Code's built-in skills (like frontend-design, code-review, security-review), one conversation covers the full cycle:

Before the bridge, anything that needed your actual machine meant leaving Cowork for a terminal. Now it all happens in one chat.

---

How it compares

There are several ways to get Claude near a machine. Here's where this bridge fits, honestly — including the cases where you don't need it:

The honest takeaway: the closest first-party option is Remote Control — same security shape (local execution, outbound-only, no inbound port). The bridge differs in that it's driven from a Cowork chat, needs no live session kept running (a background daemon survives reboots), is idempotent across dropped connections, and runs approved scripts directly when you don't need a full agent. If you live in a live Claude Code terminal session, Remote Control may suit you better — use the right tool for where you actually talk to Claude.

Feature facts above reflect Anthropic's published docs as of mid-2026 (code.claude.com/docs). They evolve — corrections welcome via issue or PR.

---

Troubleshooting

FAQ

Q: Does this work on Linux or Windows? macOS (launchd), Linux (systemd --user or the no-systemd installer path), and WSL2 on Windows (systemd in your Ubuntu distro) are supported. Native Windows (PowerShell, Task Scheduler) is not — use WSL2; see docs/WSL.md.

Q: Does it cost anything? No. It's free and open source (MIT).

Q: Do I need to be a developer to use this? You need to be comfortable pasting one terminal command. Beyond that, no — Claude does the rest. Adding custom scripts is "knows what a script is" level, not "writes code daily" level.

Q: Can my Cowork agents from different projects share one bridge? Yes — one daemon serves any number of Cowork sessions. The token is shared across sessions on the same Mac.

Q: Can I have multiple Macs? Yes — install the bridge on each Mac separately. Each generates its own token. Cowork sessions automatically use whichever Mac they're connected to.

Q: Is this an official Anthropic project? No. This is a third-party tool that fills a gap Anthropic's Cowork doesn't (yet) cover. If they ship native Cowork ↔ Mac IPC someday, you can uninstall this and switch.

Q: I'm worried about something running on my Mac without me knowing. Three protections: 1. Every command writes to ~/.cowork-to-code-bridge/processed/ so you can audit history. 2. The daemon log shows every command in real time — tail -f ~/.cowork-to-code-bridge/daemon.log. 3. You control the script whitelist — Claude can't run anything you haven't put there.

If you want even more conservative: review every Claude suggestion before agreeing to run it.

Q: How do I restrict what Claude Code can do on a task? Set CLAUDE_FLAGS in your environment before the bridge invokes Claude Code. Three recipes, from cautious to locked-down:

```bash