القائمة
Join Claude Code and Codex CLI to the Interlateral mesh in Warp panes by attaching Warp to the standard tmux socket; Warp is the visible terminal surface, tmux remains the transport.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.
Mandatory near-live communication discipline ("the Law") for the two DESKTOP agents (claude-desktop and codex-desktop) on the Interlateral mesh. Read this BEFORE any desktop-to-desktop peer communication, peer-superset, ready-rock-quartet, sprint-overseer, gate-keeper, sprint handoff, or substantial delegation. It forces correct live comms and prevents the recurring failure modes. Normal CLI agents, Warp/terminal peers, and single non-desktop workflows should ignore this skill and use the ordinary repo protocols.
Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.
| name | warp-mesh-peer |
| description | Join Claude Code and Codex CLI to the Interlateral mesh in Warp panes by attaching Warp to the standard tmux socket; Warp is the visible terminal surface, tmux remains the transport. |
| metadata | {"owner":"interlateral","version":"1.0","weight":"light"} |
| compatibility | Warp on macOS with tmux, claude, codex, and this repo on PATH. |
Use this skill when the human wants Interlateral CLI agents visible inside Warp while preserving the standard tmux mesh.
Warp is the terminal surface. tmux remains the transport. Do not use Warp Oz, Warp Drive, AppleScript, or Accessibility paste as the mesh channel.
This skill is for Claude Code and Codex CLI running inside tmux sessions that are attached from Warp panes.
It is not the Desktop join path. If Claude Desktop or Codex Desktop needs to join the mesh, use desktop-mesh-peer.
ia-claude-warpia-codex-warpSuffix variants are allowed for reviews or sprints, for example:
ia-claude-warp-reviewia-codex-warp-breakerAlways target the exact tmux session name.
Install or refresh the Warp launch configuration:
scripts/install-warp-launch-config.sh --force
Open the Warp mesh:
open "warp://launch/interlateral-warp-mesh"
This opens Warp panes attached to:
ia-claude-warpia-codex-warpIf the sessions do not exist, the wrapper creates them using the existing repo launchers.
Run either peer directly:
scripts/warp-mesh-peer.sh claude ia-claude-warp
scripts/warp-mesh-peer.sh codex ia-codex-warp
Relaunch one named peer explicitly:
scripts/warp-mesh-peer.sh --relaunch claude ia-claude-warp
scripts/warp-mesh-peer.sh --relaunch codex ia-codex-warp
The wrapper never kills an existing session unless --relaunch is supplied.
Use the same mesh helpers as the rest of the repo.
For Warp Claude:
source scripts/tmux-config.sh
claude_send_long_logged =ia-claude-warp: "ACK challenge: warp-claude-001. Reply with this nonce."
For Warp Codex:
source scripts/tmux-config.sh
agent_send_long_logged =ia-codex-warp: "ACK challenge: warp-codex-001. Reply with this nonce."
comms.md is the ledger, not the wake-up path. A valid proof has both a visible direct reply and a stamped ledger entry.
Warp attaches to existing tmux sessions. Detaching or closing a Warp pane should leave the tmux session alive. Reopening the launch config reattaches to the same session if it is healthy.
Multiple terminals can attach to the same session. They share one live TTY. Human typing and mesh injection can interleave, so check idle before sending and avoid injecting while someone is actively typing.
The wrapper checks existing sessions before attaching.
Healthy sessions must look like the requested CLI and show a usable prompt or idle state.
If a stale session exists, the wrapper prints recovery instructions and exits. It does not auto-kill.
Inspect a stale session:
source scripts/tmux-config.sh
pane_current_command ia-codex-warp
agent_capture_recent ia-codex-warp 80
Recover intentionally:
scripts/warp-mesh-peer.sh --relaunch codex ia-codex-warp
scripts/install-warp-launch-config.sh --force succeeds.open "warp://launch/interlateral-warp-mesh" opens two Warp panes.tmux -S /tmp/interlateral-agents-tmux.sock list-sessions shows ia-claude-warp and ia-codex-warp.claude_send_long_logged =ia-claude-warp: ... wakes Claude visibly and logs to comms.md.agent_send_long_logged =ia-codex-warp: ... wakes Codex visibly and logs to comms.md.--relaunch is supplied.