Squad

AI agent teams for any project. One command. A team that grows with your code.

⚠️ Alpha Software — Squad is experimental. APIs and CLI commands may change between releases. We'll document breaking changes in CHANGELOG.md.

What is Squad?

Squad gives you an AI development team through GitHub Copilot. Describe what you're building. Get a team of specialists — frontend, backend, tester, lead — that live in your repo as files. They persist across sessions, learn your codebase, share decisions, and get better the more you use them.

It's not a chatbot wearing hats. Each team member runs in its own context, reads only its own knowledge, and writes back what it learned.

Quick Start

1. Create your project

mkdir my-project && cd my-project
git init

2. Install Squad

npm install --save-dev @bradygaster/squad-cli
npx squad init

Or use npx (no install): npx @bradygaster/squad-cli — see Migration Guide if upgrading from an older version.

3. Authenticate with GitHub (for Issues, PRs, and Ralph)

gh auth login

4. Open Copilot and go

copilot

In the GitHub Copilot CLI, type /agent and select Squad. In VS Code, type /agents and select Squad.

Then:

I'm starting a new project. Set up the team.
Here's what I'm building: a recipe sharing app with React and Node.

Squad proposes a team — each member named from a persistent thematic cast. You say yes. They're ready.

All Commands (15 commands)

Command	What it does
`squad init`	Init — scaffold Squad in the current directory (idempotent — safe to run multiple times); alias: `hire`; use `--global` to init in personal squad directory, `--mode remote <path>` for dual-root mode
`squad upgrade`	Update Squad-owned files to latest; never touches your team state; use `--global` to upgrade personal squad, `--migrate-directory` to rename `.ai-team/` → `.squad/`
`squad status`	Show which squad is active and why
`squad triage`	Watch issues and auto-triage to team (aliases: `watch`, `loop`); use `--interval <minutes>` to set polling frequency (default: 10)
`squad copilot`	Add/remove the Copilot coding agent (@copilot); use `--off` to remove, `--auto-assign` to enable auto-assignment
`squad doctor`	Check your setup and diagnose issues (alias: `heartbeat`)
`squad link <team-repo-path>`	Connect to a remote team
`squad shell`	Launch interactive shell explicitly
`squad export`	Export squad to a portable JSON snapshot
`squad import <file>`	Import squad from an export file
`squad plugin marketplace add\|remove\|list\|browse`	Manage plugin marketplaces
`squad upstream add\|remove\|list\|sync`	Manage upstream Squad sources
`squad nap`	Context hygiene — compress, prune, archive; use `--deep` for aggressive compression, `--dry-run` to preview changes
`squad aspire`	Open Aspire dashboard for observability
`squad scrub-emails [directory]`	Remove email addresses from Squad state files (default: `.squad/`)

Interactive Shell

Tired of typing squad followed by a command every time? Enter the interactive shell.

Entering the Shell

squad

No arguments. Just squad. You'll get a prompt:

squad >

You're now connected to your team. Talk to them.

Shell Commands

All shell commands start with /:

Command	What it does
`/status`	Check your team and what's happening
`/history`	See recent messages
`/agents`	List all team members
`/sessions`	List saved sessions
`/resume <id>`	Restore a past session
`/version`	Show version
`/clear`	Clear the screen
`/help`	Show all commands
`/quit`	Exit the shell (or Ctrl+C)

Talking to Agents

Use @AgentName (case-insensitive) or natural language with a comma:

squad > @Keaton, analyze the architecture of this project
squad > McManus, write a blog post about our new feature
squad > Build the login page

The coordinator routes messages to the right agents. Multiple agents can work in parallel—you'll see progress in real-time.

What the Shell Does

Real-time visibility: See agents working, decisions being recorded, blockers as they happen
Message routing: Describe what you need; the coordinator figures out who should do it
Parallel execution: Multiple agents work simultaneously on independent tasks
Session persistence: If an agent crashes, it resumes from checkpoint; you never lose context
Decision logging: Every decision is recorded in .squad/decisions.md for the whole team to see

For more details on shell usage, see the commands table above.

Samples

Eight working examples from beginner to advanced — casting, governance, streaming, Docker. See samples/README.md.

Insider Channel

Want the latest features before they ship?

npm install --save-dev @bradygaster/squad-cli@insider

For insider builds:

npm install -g @bradygaster/squad-cli@insider

Note: GitHub-native distribution (npx github:bradygaster/squad) has been removed. All distribution is now via npm (see Migration Guide for details).

Agents Work in Parallel — You Catch Up When You're Ready

Squad doesn't work on a human schedule. When you give a task, the coordinator launches every agent that can usefully start — simultaneously.

You: "Team, build the login page"

  🏗️ Lead — analyzing requirements...          ⎤
  ⚛️ Frontend — building login form...          ⎥ all launched
  🔧 Backend — setting up auth endpoints...     ⎥ in parallel
  🧪 Tester — writing test cases from spec...   ⎥
  📋 Scribe — logging everything...             ⎦

When agents finish, the coordinator immediately chains follow-up work. If you step away, a breadcrumb trail is waiting when you get back:

decisions.md — every decision any agent made
orchestration-log/ — what was spawned, why, and what happened
log/ — full session history, searchable

Knowledge compounds across sessions. Every time an agent works, it writes lasting learnings to its history.md. After a few sessions, agents know your conventions, your preferences, your architecture. They stop asking questions they've already answered.

And it's all in git. Anyone who clones your repo gets the team — with all their accumulated knowledge.

What Gets Created

.squad/
├── team.md              # Roster — who's on the team
├── routing.md           # Routing — who handles what
├── decisions.md         # Shared brain — team decisions
├── ceremonies.md        # Sprint ceremonies config
├── casting/
│   ├── policy.json      # Casting configuration
│   ├── registry.json    # Persistent name registry
│   └── history.json     # Universe usage history
├── agents/
│   ├── {name}/
│   │   ├── charter.md   # Identity, expertise, voice
│   │   └── history.md   # What they know about YOUR project
│   └── scribe/
│       └── charter.md   # Silent memory manager
├── skills/              # Compressed learnings from work
├── identity/
│   ├── now.md           # Current team focus
│   └── wisdom.md        # Reusable patterns
└── log/                 # Session history (searchable archive)

Commit this folder. Your team persists. Names persist. Anyone who clones gets the team — with the same cast.

Monorepo Development

Squad is a monorepo with two packages:

@bradygaster/squad-sdk — Core runtime and library for programmable agent orchestration
@bradygaster/squad-cli — Command-line interface that depends on the SDK

Building

# Install dependencies (npm workspaces)
npm install

# Build TypeScript to dist/
npm run build

# Build CLI bundle (dist/ + esbuild → cli.js)
npm run build:cli

# Watch mode for development
npm run dev

Testing

# Run all tests
npm test

# Watch mode
npm run test:watch

Linting

# Type check (no emit)
npm run lint

Publishing

Squad uses changesets for independent versioning across packages:

# Add a changeset
npx changeset add

# Validate changesets
npm run changeset:check

Changesets are resolved on the main branch; releases happen independently per package.

The SDK: Programmable Agent Runtime

Everything above works out of the box. The sections below are for developers who want programmatic control over agent orchestration.

┌─────────────────────────────────────────────┐
│  Your Code (TypeScript)                     │
│  - createSession(), spawnParallel()         │
│  - SquadClient, EventBus, HookPipeline      │
└─────────────────────────────────────────────┘
           ↓
┌─────────────────────────────────────────────┐
│  Agent Orchestration Runtime                │
│  - Router (matchRoute, compileRoutingRules) │
│  - Charter Compiler (permissions, voice)    │
│  - Tool Registry (squad_route, etc.)        │
│  - Hook Pipeline (governance enforcement)   │
└─────────────────────────────────────────────┘
           ↓
┌─────────────────────────────────────────────┐
│  Session Pool + Event Bus                   │
│  - Each agent gets a persistent session     │
│  - Cross-session event pub/sub               │
│  - Crash recovery via session state         │
└─────────────────────────────────────────────┘
           ↓
┌─────────────────────────────────────────────┐
│  @github/copilot-sdk                        │
│  - Real-time agent streaming                │
│  - Tool execution                           │
└─────────────────────────────────────────────┘

The Key Difference

Prompt-only orchestration (v0.5.2): One 32KB prompt describes all agents, all rules, all decision-making. The coordinator is text. Agents read it, interpret it, maybe follow it.

Prompt says:
"If the agent is Keaton, apply this logic. If McManus, apply that logic."
Agent reads it (consumes tokens), decides what to do (might ignore it).

SDK orchestration (v0.6+): Rules are code. Sessions are objects. Routing is compiled. Tools are validated before they run.

Router.matchRoute(message) → { agent: 'Keaton', priority: 'high' }
TypeScript knows exactly which agent will run, with what permissions.
HookPipeline runs file-write guards BEFORE the tool executes.
No interpretation. No ambiguity. Just code.

The Custom Tools

These five tools let agents coordinate without calling you back.

`squad_route` — Hand off work to another agent

const tool = toolRegistry.getTool('squad_route');
const result = await tool.handler({
  targetAgent: 'McManus',  // Route to DevRel
  task: 'Write a blog post on the new casting system',
  priority: 'high',
  context: 'This feature launches next week',
});

What it does: Keaton (lead) routes a task to McManus (DevRel). Creates a new session for McManus, passes context, queues it with priority. McManus picks it up next.

`squad_decide` — Record a team decision

const result = await tool.handler({
  author: 'Keaton',
  summary: 'Use PostgreSQL, not MongoDB',
  body: 'We chose PostgreSQL because: (1) transactions, (2) known team expertise, (3) schema flexibility via JSONB.',
  references: ['PRD-5-coordinator', 'architecture-spike'],
});

What it does: Writes to .squad/decisions/inbox/. Every agent reads decisions.md before working. This is how Keaton's call cascades to the whole team without re-explaining.

`squad_memory` — Append to agent history

const result = await tool.handler({
  agent: 'Frontend',
  section: 'learnings',
  content: 'This project uses Tailwind v4 with dark mode plugin. Store under .styles/theme.config.ts',
});

What it does: Agents learn as they work. Next session, Frontend reads this and knows immediately. No context hunting.

`squad_status` — Query the session pool

const result = await tool.handler({
  agentName: 'Keaton',
  status: 'active',
  verbose: true,
});
// Returns: { poolSize: 5, activeSessions: 3, sessionsByAgent: {...} }

What it does: Ralph uses this to monitor work. You use it to debug ("Is Backend actually running or stalled?").

`squad_skill` — Read/write agent skills

const result = await tool.handler({
  skillName: 'react-query-setup',
  operation: 'read',
});
// Returns: skill content from .squad/skills/react-query-setup/SKILL.md

await tool.handler({
  skillName: 'auth-patterns',
  operation: 'write',
  content: 'Pattern for Clerk integration with Next.js...',
  confidence: 'high',
});

What it does: Skills are compressed learnings. Frontend writes "here's how we do auth" once. Every future Frontend session inherits it. Confidence levels let you track "we're sure" vs "we're experimenting".

The Hook Pipeline

Rules don't live in prompts. They run before tools execute.

File-Write Guards

const pipeline = new HookPipeline({
  allowedWritePaths: [
    'src/**/*.ts',
    '.squad/**',
    'docs/**',
  ],
});

// Backend tries to write to /etc/passwd
// Hook intercepts, blocks, returns:
// "File write blocked: '/etc/passwd' does not match allowed paths: src/**, ..."

Why it matters: No agent (compromised or confused) can write outside your safe zones. Not because we asked nicely in the prompt. Because code won't let them.

PII Scrubbing

const pipeline = new HookPipeline({
  scrubPii: true,
});

// Agent logs "contact brady@example.com about deploy"
// After tool execution, output is:
// "contact [EMAIL_REDACTED] about deploy"

Why it matters: Sensitive data never escapes. Automatic. Invisible to the agent.

Reviewer Lockout

const lockout = pipeline.getReviewerLockout();

// Tester rejects Backend's auth code
lockout.lockout('src/auth.ts', 'Backend');

// Next turn, Backend tries to re-write auth.ts
// Hook blocks it:
// "Reviewer lockout: Agent 'Backend' is locked out of artifact 'src/auth.ts'. Another reviewer must handle this artifact."

Why it matters: When a reviewer says "no," it sticks. The original author can't sneak a fix in. Protocol enforced.

Ask-User Rate Limiter

const pipeline = new HookPipeline({
  maxAskUserPerSession: 3,
});

// Agent has called ask_user 3 times
// Fourth attempt is blocked:
// "ask_user rate limit exceeded: 3/3 calls used for this session. The agent should proceed without user input."

Why it matters: Agents don't stall waiting for you. They decide or move on.

Event-Driven Coordination: Ralph

Ralph is your work monitor. Not a polling loop. A persistent agent session that subscribes to everything.

const ralph = new RalphMonitor({
  teamRoot: '.squad',
  healthCheckInterval: 30000,  // Every 30s
  statePath: '.squad/ralph-state.json',
});

ralph.subscribe('agent:task-complete', (event) => {
  console.log(`✅ ${event.agentName} finished: ${event.task}`);
});

ralph.subscribe('agent:error', (event) => {
  console.log(`❌ ${event.agentName} failed: ${event.error}`);
});

await ralph.start();

Ralph is always watching. When agents complete work, write decisions, or hit errors, Ralph logs it. Crash? Ralph remembers. Next session, it knows exactly where you left off.

Crash Recovery: Persistent Sessions

Sessions aren't ephemeral. They're durable.

const session = await client.createSession({
  agentName: 'Backend',
  task: 'Implement user auth endpoints',
  persistPath: '.squad/sessions/backend-auth-001.json',
});

// Agent dies mid-work (network hiccup, model timeout, whatever)
// Next time:

const resumed = await client.resumeSession(
  '.squad/sessions/backend-auth-001.json'
);

// Backend wakes up knowing:
// - What the task was
// - What it already wrote (file system has the changes)
// - Where it was in the work
// - No repetition, no lost context

The Cast: Persistent Agent Identity

Squad's secret weapon is casting. Agents aren't role-1, role-2. They're Keaton, McManus, Verbal, Fenster, Kujan. Names from The Usual Suspects (1995).

Why?

Memorable. Devs say "Keaton handles routing," not "the lead agent coordinates." It sticks.
Persistent. Same agent, same name, across every session. You build a relationship with Keaton over time.
Extensible. Adding a sixth agent? Cast them from the same universe. The identity pattern carries forward.

The casting engine compiles agent personas from the universe theme. Your .squad/agents/ folder has the actual files, but the SDK's CastingEngine makes the assignment automatic and consistent.

const casting = new CastingEngine({
  universe: 'usual-suspects',
  agentCount: 5,
});

const cast = casting.castTeam({
  roles: ['lead', 'frontend', 'backend', 'tester', 'scribe'],
});

// cast = [
//   { role: 'lead', agentName: 'Keaton', ... },
//   { role: 'frontend', agentName: 'McManus', ... },
//   { role: 'backend', agentName: 'Verbal', ... },
//   { role: 'tester', agentName: 'Fenster', ... },
//   { role: 'scribe', agentName: 'Kobayashi', ... },
// ]

What Gets Created

The SDK doesn't replace your squad directory. It uses it.

.squad/
├── team.md                # Roster — who's on the team
├── routing.md             # Routing rules — who handles what
├── decisions.md           # Shared brain — every decision
├── casting/
│   ├── policy.json        # Casting config (universe, agent count, etc.)
│   ├── registry.json      # Persistent name registry
│   └── history.json       # Who was cast when
├── agents/
│   ├── Keaton/
│   │   ├── charter.md     # Identity, expertise, voice
│   │   └── history.md     # What Keaton knows about YOUR project
│   ├── McManus/
│   │   ├── charter.md
│   │   └── history.md
│   └── ... (others)
├── skills/
│   ├── react-patterns/
│   │   └── SKILL.md       # Compressed learnings
│   ├── auth-flows/
│   │   └── SKILL.md
│   └── ... (learned over time)
├── sessions/              # Persisted sessions for crash recovery
│   ├── backend-auth-001.json
│   └── ... (auto-cleanup older than 30 days)
└── log/                   # Session history (searchable archive)

Commit all of this. It's your team's memory. Clone the repo, you get the team—with everything they've learned.

Growing Your Squad

Add an Agent

const casting = new CastingEngine({ universe: 'usual-suspects', agentCount: 6 });
const newCast = casting.castTeam({
  roles: ['lead', 'frontend', 'backend', 'tester', 'devops', 'scribe'],
});
// The SDK creates a new session for the sixth agent automatically.

Remove an Agent

// Update team.md to remove the agent, update casting config
// Old agent files move to .squad/agents/_alumni/{name}/
// Knowledge preserved forever, but not active in routing

The Tech Stack

What	Version	Why
Node.js	≥ 20.0.0	Stable async/await, strong TypeScript support
TypeScript	5.7+	Every tool, session, hook is fully typed
@github/copilot-sdk	v0.1.8+ (Technical Preview)	Real-time agent streaming, tool execution
Vitest	3.0+	Fast, concurrent test runner; great DX
esbuild	0.25+	Bundling, dead-code elimination

Testing & Coverage

npm test                # Run all tests (1551 tests across 45 files)
npm run test:watch     # Watch mode for development
npm run build          # Compile TypeScript to dist/
npm run build:cli      # Build + bundle CLI into cli.js
npm run dev            # Watch TypeScript in background
npm run lint           # Type check (tsc --noEmit)

Test coverage: 1,670 tests across 52 test files. Core modules tested:

Session lifecycle (create, resume, end)
Tool execution and validation
Hook pipeline (guards, PII scrubbing, lockouts)
Router matching and charter compilation
Parallel fan-out spawning
Event bus and subscription
Casting engine and universe selection
Ralph monitoring and health checks
Crash recovery and persistence

Known Limitations

Alpha — API and file formats may change between versions
Node 20+ — requires Node.js 20.0.0 or later
GitHub Copilot CLI & VS Code — Squad works on both CLI and VS Code
gh CLI required — GitHub Issues, PRs, Ralph, and Project Boards all need gh auth login
Knowledge grows with use — the first session is the least capable; agents improve as they accumulate history
npm distribution only — Install via npm install -g @bradygaster/squad-cli or npx @bradygaster/squad-cli. GitHub-native distribution (npx github:) is no longer supported.

Status

⚠️ Experimental — v0.8.x alpha. APIs and file formats may change between versions. We'd love your feedback — if you encounter issues, please file a bug report.

Conceived by @bradygaster.

Contributing

See CONTRIBUTING.md.

License

MIT

Name		Name	Last commit message	Last commit date
Latest commit History 894 Commits
.ai-team		.ai-team
.changeset		.changeset
.copilot		.copilot
.github		.github
.squad-templates		.squad-templates
.squad		.squad
docs		docs
images		images
packages		packages
samples		samples
scripts		scripts
templates		templates
test-fixtures		test-fixtures
test		test
.gitattributes		.gitattributes
.gitignore		.gitignore
.npmignore		.npmignore
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
CONTRIBUTORS.md		CONTRIBUTORS.md
LICENSE		LICENSE
README.md		README.md
cli.js		cli.js
index.js		index.js
package-lock.json		package-lock.json
package.json		package.json
squad-export.json		squad-export.json
squad.config.ts		squad.config.ts
tsconfig.json		tsconfig.json
vitest.config.ts		vitest.config.ts

Folders and files

Latest commit

History

Repository files navigation

Squad

What is Squad?

Quick Start

1. Create your project

2. Install Squad

3. Authenticate with GitHub (for Issues, PRs, and Ralph)

4. Open Copilot and go

All Commands (15 commands)

Interactive Shell

Entering the Shell

Shell Commands

Talking to Agents

What the Shell Does

Samples

Insider Channel

Agents Work in Parallel — You Catch Up When You're Ready

What Gets Created

Monorepo Development

Building

Testing

Linting

Publishing

The SDK: Programmable Agent Runtime

The Key Difference

The Custom Tools

squad_route — Hand off work to another agent

squad_decide — Record a team decision

squad_memory — Append to agent history

squad_status — Query the session pool

squad_skill — Read/write agent skills

The Hook Pipeline

File-Write Guards

PII Scrubbing

Reviewer Lockout

Ask-User Rate Limiter

Event-Driven Coordination: Ralph

Crash Recovery: Persistent Sessions

The Cast: Persistent Agent Identity

What Gets Created

Growing Your Squad

Add an Agent

Remove an Agent

The Tech Stack

Testing & Coverage

Known Limitations

Status

Contributing

License

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases 19

Packages 0

Uh oh!

Contributors 17

Languages

`squad_route` — Hand off work to another agent

`squad_decide` — Record a team decision

`squad_memory` — Append to agent history

`squad_status` — Query the session pool

`squad_skill` — Read/write agent skills

Packages