mesh-comms-core

Coordinates Docker containers and Pods via a unified interface for lifecycle and networking management across hosts and the cloud.

9|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/dazzaji/interlateral_agents --skill mesh-comms-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mesh-comms-core
Source: https://github.com/dazzaji/interlateral_agents/tree/main/.claude/skills/mesh-comms-core
Command: npx skills add https://github.com/dazzaji/interlateral_agents --skill mesh-comms-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Mesh Comms Core provides a reliable transport reference for Interlateral CLI mesh communication, covering discovery, direct messaging, ledger mirroring, identity stamping, idle checks, and ACK proof to keep peers synchronized.

Core Features & Use Cases

  • tmux socket and session discovery
  • direct prompt delivery with safe submission
  • comms.md ledger mirroring for auditability
  • identity stamping and nonce ACK verification
  • idle checks and safe prompt injection handling
  • shared socket: /tmp/interlateral-agents-tmux.sock as the wake-up channel

Quick Start

Boot the mesh by launching Claude Code and Codex peers and confirm the exchange via the comms ledger.

Frequently Asked Questions about mesh-comms-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover a tmux socket for reliable CLI mesh transport between agents?

CLI mesh transport discovers the tmux socket by using a shared wake-up channel at /tmp/interlateral-agents-tmux.sock, allowing peers to locate and synchronize sessions safely. This socket acts as the central discovery point for Interlateral CLI agents.

What's the best way to maintain an audit ledger for direct prompts exchanged between CLI agents?

Maintaining an audit ledger for direct prompts is handled by comms.md ledger mirroring, which mirrors all exchanged prompts to the interlateral_dna/comms.md file for full auditability. This ensures every message is recorded and verifiable.

How does identity stamping and ACK verification work for peer-to-peer CLI messaging?

Identity stamping and ACK verification work by stamping each peer with a unique identity and requiring nonce ACK proofs before collaboration proceeds. This mechanism verifies transport health and ensures peers are synchronized.

Can I use this mesh transport to safely inject prompts into idle CLI agent sessions?

Yes, you can safely inject prompts into idle CLI agent sessions. The mesh transport performs idle checks and handles safe prompt submission, ensuring that prompts are only delivered when agents are ready to receive them.

Do I need a specific environment setup to boot an Interlateral CLI mesh with Claude Code and Codex peers?

You need to launch Claude Code and Codex peers to boot the Interlateral CLI mesh. No external dependencies are required, but you must confirm the exchange via the comms ledger to verify that the transport is healthy.

Why does my CLI mesh transport lose messages between Interlateral agents during collaboration?

CLI mesh transport loses messages when ACK proofs are not verified before collaboration or when the tmux socket discovery fails. Applying identity stamping, idle checks, and ledger mirroring ensures reliable prompt delivery.