- Factory Type — Template defining the factory’s purpose and default configuration
- Factory Manager — A Convex-native Overseer agent that coordinates operations
- Team — Workers (human and agent) assigned with defined positions
- Channels — Chat channels scoped to the factory for real-time collaboration
- Dev Environments — Cloud development environments (via exe.dev) for software factories
- Budget — Allocated spend limits for the factory’s operations
Development Tasks
Factories track work through a task board: backlog → assigned → in-progress → in-review → complete. Tasks can be assigned to humans or agents. Each task links to workflow runs for traceability — when an agent executes a task, the resulting run is associated with the task record.
Factory Lifecycle
| Status | Description |
|---|---|
PROVISIONING | Channels, manager agent, and dev environment being set up |
ACTIVE | Fully operational — manager agent has a thread, channels are live |
PAUSED | Temporarily suspended — no new work dispatched, existing work can complete |
ARCHIVED | Permanently deactivated — historical data preserved for audit |
Factory Manager
The Factory Manager is a Convex-native durable agent (
Factories are provisioned from blueprints — higher-level templates that capture team composition, channel structure, environment specs, and budget limits into repeatable packages. Blueprints build on factory types, adding concrete staffing and configuration defaults.
@convex-dev/agents). It runs inside Convex with its own persistent thread and tool access. It does not route through Bridge or external gateways. The manager handles task orchestration, team coordination, status reporting, and escalation.In Burgundy: Manage factories from the projects section. →