mai-cli 1.1.1

Multi-Agent Collaboration CLI with flock-based locking and event-driven workflow

Mai CLI

Multi-Agent Collaboration CLI — flock-based coordination, event-driven workflow, zero overhead.

Mai is a command-line tool that coordinates multiple AI agents working on a shared project. It provides atomic locking, queue-based issue routing, per-agent heartbeat timeouts, and an automated daily summary loop — all backed by a simple file-based store.

---

Features

• Atomic flock locks — race-condition-free claim/complete cycles via POSIX fcntl
• Queue-based routing — issues route to the right agent with configurable SLA per queue
• Heartbeat-aware guardian — stale locks auto-release after heartbeat × 1.5 minutes
• Event-driven daily summary — ordered turn-taking with idempotent trigger/collect
• Async mirror — .mai/ internal store syncs to async/ for human visibility
• Configurable via JSON — all rules externalized to config.json; no code changes needed
• Dual output format — --format json for machine consumption, text for humans
• Dry-run mode — --dry-run previews every mutation without side effects

---

Installation

pip install mai-cli

Or install from source:

git clone https://github.com/yourname/mai-cli.git
cd mai-cli
pip install -e .

---

Quick Start

Step 1 — Initialize a project

mai project init MyProject

Step 2 — Create an issue

mai --project MyProject issue new programmer-questions "How should we handle input buffering?"

Step 3 — Have the assigned agent claim it

mai --project MyProject issue claim REQ-001

Step 4 — Mark it done

mai --project MyProject issue complete REQ-001 "Decision: ring buffer, 60Hz polling"

Step 5 — Inspect queues

mai --project MyProject queue check

---

Architecture

.mai/                        async/
├── queues/<queue>/  Issue files  <queue>/  Human-visible mirror
├── locks/           flock files  (internal only)
├── processing/      Active issues  <queue>/
├── decisions/       Conclusion logs  decisions/
├── history/         Audit logs  history/
├── events/          Daily-summary triggers  (internal only)
└── config.json      All collaboration rules

Lock protocol: When an agent claims an issue, Mai acquires an flock(2)-based file lock. The lock expires after heartbeat × 1.5 minutes if the agent fails to heartbeat. The lock guardian cron command automatically releases stale locks.

Daily summary flow: trigger → each agent write in order → collect merges all summaries into a single report.

---

Command Reference

Issue

mai issue new <queue> <title> [--ref REQ-XXX]
mai issue amend <issue-id> <remark>
mai issue claim <issue-id>
mai issue complete <issue-id> <conclusion>
mai issue list [queue]
mai issue show <issue-id>
mai issue escalate <issue-id>

Queue

mai queue check [queue] [--overdue]
mai queue blockers

Lock

mai lock check <issue-id>
mai lock force-release <issue-id>
mai lock guardian

Log

mai log history [--date YYYY-MM-DD] [--agent NAME]
mai log write <agent> <type> <summary> [status]

Daily Summary

mai daily-summary trigger
mai daily-summary write <agent> <content...>
mai daily-summary collect

Escalation

mai escalation gen <issue-id>

Bitable

mai bitable sync-status
mai bitable retry

Project

mai project init <project-name>

---

Configuration

Edit .mai/config.json in your project root:

{
  "queues": {
    "programmer-questions": {
      "handler": "designer",
      "sla_minutes": 120,
      "id_prefix": "REQ"
    }
  },
  "agents": {
    "programmer": { "heartbeat_minutes": 17 },
    "designer":   { "heartbeat_minutes": 29 }
  },
  "daily_summary_order": ["programmer", "designer", "architect", "narrative", "techartist"]
}

Legacy field compatibility

owner → handler, sla_hours → sla_minutes are automatically converted.

---

Supported Platforms

• OS: Linux / macOS (POSIX required for flock)
• Python: 3.8, 3.9, 3.10, 3.11, 3.12

---

License

MIT License — see LICENSE for the full text.