Agent orchestration platform - multi-agent spawning, tickets, boards, and workflows
2026-11-09
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Agent orchestration platform for AI labor. Spin up workers for all work, on demand.
Themed agents, including billionaires - Finally, they work for us.
⚠️ Beta Software — Under active development. Commands and APIs may change between versions, and bugs are actively being squashed.
Let's get you shippingBook a call - I'm happy to help you get prlt running or chat feedback, ideas, multi-agent workflows, and the future of work/labor (and economic labor theory..)
TLDR
prlt is an agent orchestration platform for AI labor. Spin up workers on demand, coordinate multi-agent development from one CLI. Isolated workspaces, secure containers, persistent state.
brew install chrismcdermut/proletariat/prlt # macOS (Homebrew)
# or
npm install -g @proletariat/cli # any platform (npm)
prlt new
prlt ticket create --title "Add OAuth" --category feature
prlt work spawn # Interactive: select tickets, environment, action
Agent spawns in its own branch, writes code, opens PR. You review and merge.
Why prlt?
Isolated - Each agent gets its own git branch. No conflicts.
Secure - Docker containers, sandboxed from your host.
Durable - Tmux sessions persist. Close window, agent keeps working.
Trackable - One database, one CLI, all your agents.
Ephemeral - Spawn agents on demand. They work, they PR, they're done.
Structured - Tickets provide structured context, not freeform chat.
Persistent - Tickets accumulate context over time. Hand off between agents.
Agent-native - --json mode lets AI agents drive the CLI programmatically.
Spawn agents to implement, groom, or review—not just write code.
Interactive Menus
prlt work guides you through project and ticket selection:
Choose your operation—start a single agent, batch spawn, or watch a column:
Select tickets to spawn, grouped by priority:
Deep Dive
Problem
Solution
Agents conflict with each other's changes
Isolated - Each agent gets its own git branch and worktree
Agents run unsandboxed on your machine
Secure - Docker containers, sandboxed from your host (looking into host sandbox options)
You lose track of who's doing what
Trackable - All state in one SQLite database, one CLI
Structured - Tickets with requirements, acceptance criteria
Starting agents is heavyweight
Ephemeral - Spawn on demand, they work, they PR, they're done
Context lost between agent runs
Persistent - Tickets accumulate context, hand off between agents
Installation
Homebrew (recommended)
brew install chrismcdermut/proletariat/prlt
Works on both Apple Silicon (arm64) and Intel (x86_64) Macs. No compiler needed.
Upgrade:
brew update
brew upgrade prlt
npm / pnpm (all platforms)
npm install -g @proletariat/cli
# or
pnpm install -g @proletariat/cli
pnpm 10+ note: pnpm 10 blocks native addon build scripts by default. If prlt fails with a native module error after install, run pnpm approve-builds in the global store and reinstall, or use npm / brew instead.
Verify:
prlt --version
MCP Server
prlt includes a built-in MCP server with 100+ tools. Add it to your AI client:
Work container with lifecycle (draft → active → complete)
Ticket
Individual work item with requirements and acceptance criteria
Spec
Static documentation (can span projects, linked to epics)
Workflow
Status flow configuration (can be shared across projects)
Phase
Stage in a workflow
Status
Ticket state within a phase
Action
Reusable prompt/action templates
Agent (Staff)
Persistent named agent with dedicated workspace
Agent (Temp)
Ephemeral agent spawned for a single ticket
Execution
Running agent session on a ticket
Display
Terminal (new tab) or Background (detached)
Example Workflow
A workflow defines how tickets move through your process. Projects reference a workflow, and multiple projects can share the same one.
Kanban Workflow
├── Backlog # New tickets land here
├── In Progress # Agent working (prlt work spawn)
├── Review # PR ready (prlt work ready)
└── Done # Merged (prlt work complete)
Scrum Workflow
├── Backlog
├── Sprint
│ ├── To Do
│ ├── In Progress
│ └── In Review
└── Done
Tickets flow through statuses as work progresses. Agents automatically move tickets when they start work, open PRs, or complete tasks.
Workspace Structure
Each agent gets a copy of all repos (repo scoping coming soon). Work happens on isolated branches.
my-project/
├── .proletariat/
│ └── workspace.db # Tickets, executions, state
├── repos/
│ ├── frontend/ # Your repos
│ ├── backend/
│ └── infra/
└── agents/
├── staff/
│ └── alice/ # Named agent with persistent workspace
│ ├── frontend/
│ ├── backend/
│ └── infra/
└── temp/
├── agent-abc123/ # Ephemeral: Working on TKT-042 (OAuth)
│ ├── frontend/ # All repos on branch: feat/TKT-042-oauth
│ ├── backend/
│ └── infra/
└── agent-def456/ # Ephemeral: Working on TKT-043 (API)
├── frontend/ # All repos on branch: feat/TKT-043-api
├── backend/
└── infra/
Agent Naming Themes
Themes control how agents are named. Staff agents use theme names directly (e.g., bezos, camry). Ephemeral agents add an adjective prefix (e.g., bold-bezos, keen-camry). Currently ephemeral names also include a number suffix (bold-bezos-1), but this will be removed soon.
Built-in Themes:
Theme
Description
Example Names
billionaires
Tech founders & executives (default)
musk, gates, bezos
toyotas
Toyota vehicle models
camry, supra, tacoma
companies
Major tech companies
stripe, vercel, linear
billionaires — Finally, they work for us.
Theme Commands:
prlt agent themes list # List available themes
prlt agent themes set billionaires # Set active theme
prlt agent themes create mytheme # Create custom theme
prlt agent themes add-names mytheme # Add names to custom theme
prlt work spawn TKT-042 TKT-043 --action implement --mode docker
Each agent works in its own branch. No conflicts.
Scaling: The main limit is your machine. 50+ concurrent agents is achievable—depends on CPU, RAM, and whether you're running Docker or host mode.
Monitor running agents with prlt execution:
flowchart LR
subgraph You
spawn[prlt work spawn]
end
subgraph Agents
A1[Agent 1<br/>TKT-042 OAuth]
A2[Agent 2<br/>TKT-043 Rate Limit]
A3[Agent 3<br/>TKT-044 Notifications]
end
subgraph GitHub
PR1[PR #101<br/>feat/TKT-042-oauth]
PR2[PR #102<br/>feat/TKT-043-rate-limit]
PR3[PR #103<br/>feat/TKT-044-notifications]
end
spawn --> A1
spawn --> A2
spawn --> A3
A1 --> PR1
A2 --> PR2
A3 --> PR3
Agent-created PRs ready for review:
Command Reference
Run prlt <command> --help for flags and options.
Use Cases
Parallel Feature Development
# Create tickets for each feature
prlt ticket create --title "Add OAuth" --category feature
prlt ticket create --title "Add API rate limiting" --category feature
prlt ticket create --title "Add email notifications" --category feature
# Spawn all three in parallel (Docker for isolation)
prlt work spawn TKT-001 TKT-002 TKT-003 --mode docker
# Watch the board as they work
prlt board watch
Three agents, three branches, three PRs. You review and merge.
Bug Bash
# Spawn all bugs at once
prlt work spawn --all --column Backlog --category bug
# Or pick specific ones
prlt work spawn TKT-010 TKT-011 TKT-012
If you must use Bun, ensure Node.js 22 (LTS) is also installed and set better-sqlite3 to use its prebuilt binaries:
npm rebuild better-sqlite3
npm EACCES: permission denied
Symptom: npm install -g @proletariat/cli fails with EACCES: permission denied on /opt/homebrew/lib/node_modules or /usr/local/lib/node_modules.
Fix: Configure npm to use a user-writable directory:
mkdir -p ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH="$HOME/.npm-global/bin:$PATH"
# Add the export line to your ~/.zshrc or ~/.bashrc
npm install -g @proletariat/cli
Or use Homebrew instead (macOS):
brew install chrismcdermut/proletariat/prlt
Native module errors after install
Symptom: prlt runs but crashes with better_sqlite3.node or ABI mismatch errors.
Fix:
# Rebuild for the current Node version
npm rebuild better-sqlite3
# Verify it works
node -e "require('better-sqlite3')"
# If still failing, reinstall
npm install -g @proletariat/cli --force