indus-swarms

A lightweight extension for the indusagi CLI that brings Claude-style agent teams to your Pi workflows. The leader process manages shared task lists, mailboxes, and team status while spawning autonomous teammates (workers) that claim, execute, and report on tasks.

What it provides

1. Team coordination primitives — shared task list files, dependency tracking, and auto-claiming keep multiple agents working without manual juggling.
2. Messaging layer — direct DM mailboxes, broadcasts, and steering instructions let you nudge teammates from the leader session.
3. Lifecycle control — graceful shutdown, kill, prune, and cleanup keep team artifacts tidy; widgets show real-time status.
4. Model/workspace control — spawn teammates with fresh or branched contexts, shared workspaces or per-agent git worktrees, and optional plan/approval flows.
5. Hook + widget support — leader-side hooks can enforce quality gates and the /tw widget surfaces tasks, inboxes, and shortcuts like m for message and t to toggle task view.

Installation

Requires Node 20+ and the indusagi CLI. Install once per machine, then install the extension however you prefer:

npm install indusagi indusagi-coding-agent

Option A — install from npm:

indusagi install npm:indus-swarms

Option B — load directly for development:

indusagi -e /Users/varunisrani/indusagi-ts/indus-swarms/extensions/teams/index.ts

Option C — install from the local folder:

indusagi install /Users/varunisrani/indusagi-ts/indus-swarms

Once installed, run indusagi as usual and the extension auto-discovers.

Quick usage

1. Start indusagi.
2. Confirm the extension is active with /team id or /team help.
3. Spawn teammates manually:

   /team spawn alice shared
   /team spawn bob branch worktree

4. Create tasks and assign them:

   /team task add alice: Explore AGENTS.md
   /team task list
   /team task assign 1 bob

5. Communicate:
   • /team dm <name> <msg> — mailbox DM
   • /team broadcast <msg> — message everyone
   • /team steer <name> <msg> — steering for RPC workers
6. Monitor progress with /tw (or /team panel) and use shortcuts (t for current agent tasks, m for a DM, k to kill, etc.).
7. When you are done:

   /team shutdown
   /team cleanup

Alternatively, /swarm <task> lets the model spawn teammates, delegate tasks, and coordinate the work for you.

Environment variables

| Variable | Purpose | Default | | --- | --- | --- | | INDUS_TEAMS_ROOT_DIR | Root directory for all team artifacts (task lists, mailboxes, sessions). Defaults to ~/.indusagi/agent/teams (legacy ~/.pi/agent/teams also works). | ~/.indusagi/agent/teams | | INDUS_TEAMS_DEFAULT_AUTO_CLAIM | Auto-claim new tasks when teammates idle. | 1 | | INDUS_TEAMS_STYLE | UI style (normal, soviet, pirate, or custom). | normal | | INDUS_TEAMS_HOOKS_ENABLED | Enable leader-side hooks/quality gates. | 0 | | INDUS_TEAMS_HOOKS_DIR | Directory holding on_idle, on_task_completed, on_task_failed hooks. | <teamsRoot>/_hooks | | INDUS_TEAMS_HOOK_TIMEOUT_MS | Hook timeout in milliseconds. | 60000 | | INDUS_TEAMS_HOOKS_FAILURE_ACTION | Policy when a hook fails (warn, followup, reopen, reopen_followup). | warn | | INDUS_TEAMS_HOOKS_MAX_REOPENS_PER_TASK | Max reopen count when hooks requeue tasks. | 3 | | INDUS_TEAMS_HOOKS_FOLLOWUP_OWNER | Owner of follow-up tasks created after hook failures (member, lead, none). | member |

License

MIT