Autonomous Company
Autonomous Company was formerly Auto-Company. For existing installations, follow the one-time v3 migration guide before starting.
An AI company framework for continuous autonomous work
Powered by Agentic Workflows, this project provides 14 AI agent role definitions, each drawing on an expert's approach to its domain. The team can research products, make decisions, and write code autonomously within human-configured goals, permissions, and budgets. Deployment, publication, and marketing depend on the tools and authorization available; continuous operation depends on services and model availability.
Powered by Claude Code (default) and Codex CLI on macOS + Windows/WSL, with a local dashboard on both hosts.
Optional Cursor and OpenAI-compatible adapters require explicit configuration. See the adapter guide for their capabilities and limits.
v2.2.0: A refined Dashboard with continuous work journals, smoother navigation and improved mobile layouts.
🎬 Dashboard and Product Preview
Interface demo using recorded work; unavailable runtime fields use sample values. Click an image to view it at full size. Capture sources and reproduction.
✨ What Is This?
You start a loop. Each cycle reads the shared work summary, decides what to do, forms a team as needed, executes, updates the summary, and waits before the next cycle. Team creation depends on the model and engine capabilities; errors, budget limits, or a pause request can stop continuation.
daemon (launchd / systemd --user, auto-restart on crash)
└── scripts/core/auto-loop.sh (continuous loop)
├── reads PROMPT.md + consensus.md
├── LLM CLI call (Codex CLI / Claude Code)
│ ├── reads CLAUDE.md (charter + guardrails)
│ ├── reads .claude/skills/team/SKILL.md (teaming method)
│ ├── forms an Agent Team as needed
│ ├── executes: research, coding, deploy, marketing
│ └── updates memories/consensus.md (work summary)
├── failure handling: rate-limit wait / circuit breaker / consensus rollback
└── sleep -> next cycle
Each cycle is an independent CLI call. memories/consensus.md is the main work summary loaded for the next cycle. Product files, repositories, configuration, identity records, logs, and usage data also persist across cycles.
🗂️ Product Center
The local Product Center brings explicitly connected product runs into one catalog. Switching products changes only what you are viewing; importing an existing run starts as read-only and never starts a model by itself.
| Capability | What it does |
|---|---|
| Product catalog | Search and open connected products while keeping each product's identity, history, usage and recorded outcomes separate. |
| Safe import | Connect an existing run or source for read-only review first; incompatible or incomplete sources stay unavailable for execution. |
| Explicit work requests | Continue a product or prepare a new exploration only after you submit a request. Viewing and refreshing do not create work. |
| Parallel work | Run up to four projects at once by default; adjust the limit or choose unlimited. Each project retains its place until its continuous loop and cleanup finish. |
| Batch creation and templates | Create groups with different models, reasoning levels and project counts. Save configurations as templates; queued work keeps the choices made when submitted. |
| Faster browsing | A compact catalog, preview choices and consistent work reports make products easier to find and follow. Open a product from its row, with keyboard support throughout. |
| Visible recovery | Preparation, failures, protective pauses and uncertain states remain visible after reload so you can review them before retrying or resuming the queue. |
Start it from the repository, then open http://127.0.0.1:8810/center:
# macOS / WSL
make center
# Windows PowerShell
.\scripts\windows\center-win.ps1
See the Product Center guide for source registration, execution-domain setup, queue controls and recovery behavior.
🧩 Generated Applications
The example catalog contains 22 independently runnable public examples, including 14 newly completed products and selected historical work. Each entry provides startup instructions, limitations and provenance; new local runs continue to write into projects/.
The examples cover professional data review, image delivery, shared meals, travel pacing and family creation. Published copies preserve the original product direction while refining components and repairing real interactions; original reports and unsuccessful conclusions are not rewritten for the showcase.
Frontend work uses the B design baseline adapted from Anthropic, followed by a dedicated finishing pass once the core flow works. The pass preserves the product’s identity and improves components, copy and responsive behavior. The refinement study and redesign comparison retain their original evidence and limits.
🚀 Where To Start (By Platform)
- Windows user