菜单
Join Claude Desktop or Codex Desktop to the Interlateral mesh as a desktop peer with its own tmux inbox session, identity, direct ACK, and ledger mirror. This is separate from the standard CLI init flow.
用 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 | desktop-mesh-peer |
| description | Join Claude Desktop or Codex Desktop to the Interlateral mesh as a desktop peer with its own tmux inbox session, identity, direct ACK, and ledger mirror. This is separate from the standard CLI init flow. |
| metadata | {"owner":"interlateral","version":"1.0","weight":"light"} |
| compatibility | Desktop agent plus shell access to the Interlateral agents repo. |
Use this skill when a desktop agent needs to join the live Interlateral comms mesh.
Desktop peers are not launched by init or me.sh. They join separately with their own inbox session and must prove both direct and ledger comms.
This skill is self-contained for desktop peer onboarding. Use mesh-comms-core first if the shared socket, helper scripts, or current CLI sessions are not already known.
Every desktop peer must:
/tmp/interlateral-agents-tmux.sockcodex-desktop or claude-desktopcomms.md pollinginterlateral_dna/comms.md as the audit ledgerDesktop peers are full mesh peers, but they are manually joined peers. The standard init skill only launches the CLI duo.
Default peer policy: desktop peers are opt-in. Do not join Claude Desktop, Codex Desktop, Antigravity Desktop, Gemini, or Antigravity CLI to a routine workflow unless the human explicitly selects that peer.
Note: Claude Desktop and Codex Desktop are passive inbox peers — a human or the
desktop app must read the inbox; there is no programmatic live channel. The
Antigravity CLI is different: it joins as a native CLI peer with real live
comms. To put Antigravity on the mesh, use the agy-cli-peer skill, not this
one. See ANTIGRAVITY.md for the full picture.
Use stable sender identities:
claude-desktopcodex-desktopUse stable inbox sessions:
ia-claude-desktopia-codex-desktopcd "${INTERLATERAL_AGENTS_REPO:-$PWD}"
source scripts/tmux-config.sh
tmux -S "$TMUX_SOCKET" new-session -d -s ia-codex-desktop \
"bash -lc 'echo Codex Desktop mesh inbox ready; exec cat -v'"
Adjust the session name and text for Claude Desktop.
The inbox is intentionally simple: it gives CLI peers a direct tmux target for messages to the desktop-side operator.
To observe the inbox:
tmux -S "$TMUX_SOCKET" capture-pane -t ia-codex-desktop -p -S -120
Desktop peers should send to CLI peers with the same helper scripts:
node interlateral_dna/cc.js send "message to Claude CLI"
node interlateral_dna/codex.js send "message to Codex CLI"
node interlateral_dna/gemini.js send "message to Gemini CLI" # only if Gemini was explicitly selected
Set sender identity before sending when possible:
export INTERLATERAL_SENDER=codex-desktop
export INTERLATERAL_AGENT_TYPE=codex-desktop
For codex-desktop, target ia-codex-desktop.
For claude-desktop, target ia-claude-desktop. If there is no dedicated helper, use agent_send_logged against that inbox session so the direct message is also mirrored to comms.md.
source scripts/tmux-config.sh
agent_send_logged ia-codex-desktop "ACK challenge: desktop-ack-123. Reply in comms.md and direct to ia-codex."
The helper uses the same Escape-then-Enter TUI submission pattern as CLI peers. Do not rely on raw tmux send-keys unless you are deliberately troubleshooting the transport.
Use a nonce challenge:
Desktop mesh ACK challenge: desktop-ack-YYYYMMDD-HHMMSS.
Reply with the nonce, your sender identity, and the target CLI session you can reach.
The desktop peer is joined only when:
interlateral_dna/comms.mdDESKTOP_MESH_PEER_READY: yes
DESKTOP_IDENTITY: codex-desktop|claude-desktop
INBOX_SESSION: ia-codex-desktop|ia-claude-desktop
DIRECT_ACK: pass/fail
LEDGER_ACK: pass/fail
NOTES: ...