Fix Codex bridge tool guidance

[axeldelafosse]

Summary

• centralize bridge tool naming in bridge-guidance.ts, including shared BridgeTool, bridgeToolName(...), and quotedBridgeTool(...) helpers so paired and tmux prompts derive the same tool strings from one place
• update paired-loop prompts, review handoff guidance, and forwarded bridge prompts to reference the correct bridge tool name for the current agent
• update paired tmux guidance so Claude uses the dynamic tmux bridge server tool names and Codex uses the loop bridge MCP tool names
• remove duplicated bridge helper logic from paired-loop and tmux after moving it into the shared guidance module
• add regression coverage for both resolved bridge tool names and quoted bridge tool names

Root Cause

Codex and Claude do not expose the same bridge tool identifiers. Some prompts still referenced generic tool names even when the available tool was namespaced, and the tool-formatting logic was duplicated across call sites, which made the guidance easier to drift out of sync with the actual MCP surface.

Impact

Paired runs and tmux sessions now tell each agent to call the exact bridge tools available in that environment, and the shared helper path reduces the chance that future prompt changes reintroduce mismatched bridge tool names.

Validation

• bun test tests/loop/bridge-guidance.test.ts tests/loop/paired-loop.test.ts tests/loop/tmux.test.ts
• bun run check

[gemini-code-assist]

Code Review

This pull request implements namespacing for Codex bridge tools by introducing a bridgeToolName helper and updating guidance prompts across the codebase to use namespaced tool names (e.g., mcp__loop_bridge__...). The reviewer suggests centralizing the BridgeTool type and the quotedBridgeTool helper within bridge-guidance.ts to eliminate duplication and improve maintainability across paired-loop.ts and tmux.ts.

[gemini-code-assist]

The BridgeTool type is used in multiple files (paired-loop.ts, tmux.ts). Exporting it from here centralizes the definition and avoids duplication.

Suggested change

	type BridgeTool = "bridge_status" | "receive_messages" | "send_message";
	export type BridgeTool = "bridge_status" | "receive_messages" | "send_message";

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

The quotedBridgeTool helper is currently duplicated in paired-loop.ts and tmux.ts. It should be defined once here and exported to improve maintainability. Ensure that the resulting strings are used within newline-delimited JSON for agent communication.

Suggested change

	export const bridgeToolName = (agent: Agent, tool: BridgeTool): string =>
	agent === "claude" ? tool : codexBridgeToolName(tool);
	export const bridgeToolName = (agent: Agent, tool: BridgeTool): string =>
	agent === "claude" ? tool : codexBridgeToolName(tool);
	export const quotedBridgeTool = (agent: Agent, tool: BridgeTool): string =>
	'"' + bridgeToolName(agent, tool) + '"';

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

Import the shared quotedBridgeTool helper from bridge-guidance.ts to reduce local duplication.

Suggested change

	import { bridgeToolName } from "./bridge-guidance";
	import { bridgeToolName, quotedBridgeTool } from "./bridge-guidance";

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

This type is now exported from bridge-guidance.ts. Removing the local definition avoids redundancy.

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

This helper has been moved to bridge-guidance.ts and should be removed from here.

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

Import the shared quotedBridgeTool helper from bridge-guidance.ts instead of defining it locally.

Suggested change

	bridgeToolName,
	bridgeToolName,
	quotedBridgeTool,

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.

[gemini-code-assist]

This helper is duplicated and should be removed in favor of the shared implementation in bridge-guidance.ts.

References

1. When communicating between agents in a paired tmux runtime, use newline-delimited JSON on stdout for agent CLIs, as Content-Length framing can break registration/connection.