desktop-mesh-peer

Connect Claude Desktop or Codex Desktop to the Interlateral mesh as an isolated inbox peer.

9|Updated Apr 2, 2026

Search Tags:#tmux #desktop #ledger #mesh #peer #inbox-session #ACK

Ready to run

npx skills add https://github.com/dazzaji/interlateral_agents --skill desktop-mesh-peer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: desktop-mesh-peer
Source: https://github.com/dazzaji/interlateral_agents/tree/main/.claude/skills/desktop-mesh-peer
Command: npx skills add https://github.com/dazzaji/interlateral_agents --skill desktop-mesh-peer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Establish an isolated desktop mesh peer with a dedicated inbox session on the shared socket
Mirror key messages to interlateral_dna/comms.md for audit and compliance
Validate join with a nonce challenge visible in both the direct path and the ledger to ensure integrity

Quick Start

Create a dedicated desktop inbox session on the shared socket and join the Interlateral mesh with a verifiable identity and ledger mirror.

Frequently Asked Questions about desktop-mesh-peer

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

FAQPage Schema

How do I connect Claude Desktop or Codex Desktop to a mesh network as a peer?▼

To connect Claude Desktop or Codex Desktop to the Interlateral mesh, you establish an isolated desktop peer with a dedicated TMUX inbox session on the shared socket, providing stable identity and direct ACK delivery.

What is a desktop mesh peer and when do I need a dedicated inbox session?▼

A desktop mesh peer is an isolated node connecting Claude Desktop or Codex Desktop to the Interlateral mesh. You need a dedicated TMUX inbox session when a human operator requires stable identity and ledger-backed visibility for direct messaging.

How does ledger mirroring to comms.md work for desktop mesh peers?▼

Ledger mirroring for desktop mesh peers copies key messages to interlateral_dna/comms.md, providing audit and compliance visibility. A nonce challenge validates the join across both direct and ledger paths to ensure data integrity.

Can I use a desktop mesh peer alongside the standard CLI init flow?▼

Yes, establishing a desktop mesh peer is separate from the standard CLI init flow. It provides a dedicated TMUX inbox on the shared socket specifically for desktop onboarding scenarios needing isolated identity and direct ACK delivery.

What's the best way to verify desktop peer integrity when joining the mesh?▼

The best way to verify desktop peer integrity when joining the mesh is through a nonce challenge. This validation confirms join integrity by ensuring the challenge is visible in both the direct messaging path and the ledger mirror.

Do I need dependencies or components to set up a desktop mesh peer?▼

No external dependencies or components are required to set up a desktop mesh peer. The Skill establishes the TMUX inbox session on the shared socket and configures ledger mirroring to interlateral_dna/comms.md natively.