Company mode
Build a firm of agents: a CEO agent, departments, leads, and members, each department in its own worktree, every cost tracked.
Company mode turns "a chatbot you talk to" into "a firm you describe goals to." You build an organization of agents the way you would build a company: a CEO agent, departments, leads, and members. Then you describe the goal, and the firm divides the work, reviews itself, and reports back while you watch every move.
The hierarchy
nala (CEO agent)
├── jade — Engineering
│ ├── alex · kai · nova
├── onyx — Design
│ ├── ember · sable
└── meadowbrook — Product
└── indigo
The CEO agent takes the mission, decomposes it, and tasks its departments. Leads run their departments and report up. Members do the work in isolated environments. Delegation is depth-limited and cycle-detected, so the org chart cannot recurse into itself.
The preset roster
40+ agent presets across Engineering, Design, PM, Testing, Sales, Marketing, Product, and Specialized categories: software-architect, backend-architect, frontend-developer, ui-designer, product-manager, mcp-builder, and many more. Presets bundle a role prompt, skills, and default tools, so a "ui-designer" arrives already thinking like one.
Built-in company templates give you a working firm in one click, and you can save and restore your own configurations.
Isolation and accountability
- Git worktrees. Each department works in its own isolated worktree. Engineering's branch never collides with Design's, and every department's output is a clean diff you can review.
- Cost tracking. Per-member cost estimation with session duration tracking, so "what did the firm cost me today?" has a precise answer.
- Approvals. Critical actions (spawns, dangerous operations) route through the risk-tiered approval system.
- Message routing. Intra-firm communication rides A2A with queues and inboxes, and the wait graph breaks message loops automatically.
A typical session
- Open the Company view (
Ctrl+Shift+O) and pick a template, or provision departments from presets. - Describe the goal to the CEO agent: "Ship the onboarding flow: spec, implementation, tests, and a review."
- The CEO fans the mission out to departments; leads claim tasks; members work their worktrees.
- Reviews happen inside the firm (a reviewer agent questions the builder over A2A) before anything reaches you.
- You watch progress in the fleet view (
Ctrl+Shift+A), approve anything critical, and read the final diff per worktree.
Provisioning spins up real agent workspaces (Claude Code instances by default), each with its own session, so the firm survives reboots like everything else in nala.
When to use it
Company mode shines on work that naturally divides: a feature with frontend, backend, tests, and docs; a migration with per-module owners; a review pipeline with authors and critics. For one focused bug, a single nala session is faster. The skill is knowing when you need a firm and when you need a scalpel.