multi-agent

Coordinate multi-agent collaboration across tmux panes with scripts and jq.

Updated Aug 29, 2025
One-click install
npx skills add https://github.com/data-desk-eco/afungi-logistics --skill multi-agent-data-desk-eco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent
Source: https://github.com/data-desk-eco/afungi-logistics/tree/main/.claude/skills/multi-agent
Command: npx skills add https://github.com/data-desk-eco/afungi-logistics --skill multi-agent-data-desk-eco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, tmux, and includes scripts (resource) components.

What problem does it solve?

Facilitates coordinated, multi-user coding and collaboration by providing a structured toolkit of scripts that manage chat, history, sessions, and task tracking within a shared tmux environment.

Core Features & Use Cases

  • Lightweight, script-driven collaboration across Claude Code sessions using a shared tmux session.
  • Centralized chat, history, and status coordination to avoid conflicts and streamline teamwork.
  • Useful for engineering teams coordinating work streams, pair programming, and remote teammates in a repeatable workflow.

Quick Start

Start a shared multi-agent session and begin coordinating agents using the provided scripts.

Frequently Asked Questions about multi-agent

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

FAQPage Schema
How do I coordinate multiple Claude Code sessions in a shared terminal environment?

You can coordinate multiple Claude Code sessions by running them in separate tmux panes within a shared session. This Skill provides scripts using tmux and jq to manage chat logs, history, and task tracking across those panes for synchronized teamwork.

Can I share a chat log and task status across tmux panes for pair programming?

Yes, sharing a chat log and task status across tmux panes is supported by frontmatter-based discovery and script-driven coordination. It centralizes communication and history tracking to prevent conflicts during pair programming or remote team workflows.

Do I need jq and tmux installed to run multi-agent shell scripts?

Yes, jq and tmux are required dependencies. The toolkit relies on tmux to manage multiple terminal panes for agent sessions and jq to parse and coordinate the structured data used for chat and task tracking.

What is the best way to manage multi-agent collaboration without conflicting terminal outputs?

The best way to manage multi-agent collaboration without terminal conflicts is using a centralized, script-driven toolkit within a shared tmux session. This approach coordinates status tracking and chat history, ensuring agents react to prompts without overwriting each other's work.

Are there limitations to using shell scripts for coordinating agent sessions in tmux?

Limitations include relying entirely on shell scripts, tmux, and jq for coordination, which means the toolkit is bound to terminal-based environments and requires manual session management for complex, multi-agent task tracking workflows.