init

Bootstrap an Interlateral two-agent CLI mesh with Claude Code and Codex.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly and reliably bootstrap the standard Interlateral two-agent CLI mesh from a bootstrap agent, configuring the mesh and launching the default Claude Code and Codex peers.

Core Features & Use Cases

  • Automated startup of the two-agent mesh with the standard defaults (Claude Code and Codex) and a ready phrase.
  • Clear bootstrap operator role that ensures the bootstrap agent does not join the mesh as a peer.
  • Built-in preflight, ACK handshake verification, and readiness check to ensure a stable mesh.

Quick Start

Run ./me.sh from the repository root to bootstrap the standard two-agent CLI mesh.

Frequently Asked Questions about init

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

FAQPage Schema
How do I bootstrap a two-agent CLI mesh with Claude Code and Codex?

To bootstrap a two-agent CLI mesh, run ./me.sh from the repository root to configure and launch Claude Code in ia-claude and Codex in ia-codex with default models, validating the ACK handshake and waiting for the ready phrase within a tmux session.

What prerequisites do I need to launch an Interlateral two-agent mesh?

Launching an Interlateral two-agent mesh requires access to the repository, a functioning tmux socket at /tmp/interlateral-agents-tmux.sock, and the ability to run me.sh with appropriate environment variables configured.

How does the ACK handshake validation work during CLI mesh startup?

ACK handshake validation checks the two-agent mesh connection by configuring Claude Code and Codex peers, verifying the acknowledgment signal, and waiting for a ready phrase to ensure a stable mesh within the tmux session.

Does the bootstrap agent join the two-agent mesh as a peer?

No, the bootstrap agent does not join the two-agent mesh as a peer; it maintains a clear bootstrap operator role to configure and launch the standard Claude Code and Codex agents without participating in the mesh itself.

Why is my two-agent CLI mesh failing to start in tmux?

A two-agent CLI mesh fails to start if the tmux socket at /tmp/interlateral-agents-tmux.sock is not functioning, repository access is missing, or me.sh cannot run due to improper environment variables.

What does the init bootstrap script do for the Interlateral mesh?

The init bootstrap script automatically performs preflight checks, configures default Claude Code and Codex peers, validates the ACK handshake, and waits for the ready phrase to establish a stable two-agent CLI mesh.