concept
Created: 2026-04-29
Updated: 2026-04-29

Sources:

crew-referencecrew-state
conceptsLast updated 2026-04-29

Crew Coordination

Workspace file coordination — the simple, audit-trail-friendly pattern The Ghost Squad uses to coordinate multi-agent work without exotic protocols.

Summary

Workspace file coordination — the simple, audit-trail-friendly pattern The Ghost Squad uses to coordinate multi-agent work without exotic protocols.

The Pattern

Agents communicate by reading and writing files in crew/:

crew/
├── inbox/          # New tasks (write here to assign)
├── outbox/         # Completed work (read here for results)
├── briefs/         # Intelligence output
├── state.json      # Global crew state
└── logs/           # Activity logs

Why Files?

Approach
Pros
Cons
Files
Audit trail, simple, persistent, inspectable
Slightly slower than memory
Memory/Variables
Fast
Lost on restart, invisible
Database
Structured, queryable
Overhead, schema migration
Message Queue
Real-time
Complexity, single point of failure

Conventions

1. inbox/ — Write tasks as JSON or Markdown files

2. outbox/ — Write completion reports with timestamps

3. state.json — Update after every significant action

4. Logs — Append, don't overwrite

State Format

crew/state.json tracks agent status, current tasks, and queues. Every agent updates their own entry.

Relationships