bridge-file

Cross-project communication is automated by reading and writing to a shared bridge directory at ~/.claude/bridge, passing issues, notes, specs, and decisions between concurrent Claude sessions to keep work synchronized.

Traceability is maintained through an append-only log history within the bridge files, and all bridge-originated tasks must be explicitly closed with a final response appended to the log. This ensures a permanent, sequential record of all cross-project decisions and interactions.

No manual configuration is needed for project pairs because the system auto-detects them and provides a structured bridge directory automatically. You simply instruct the skill to check or write a bridge message and follow the prompts to complete the cross-project task.

Safe bridging requires explicit actions for both reads and writes to the shared directory, preventing accidental overwrites or data loss. This strict interaction protocol ensures that open bridge tasks are properly managed and closed with a final appended response.

Leaving an open bridge task incomplete breaks the open-loop coordination rules, which require all bridge-originated tasks to be explicitly closed with a final response appended to the bridge file to maintain strict traceability.