StackMap
Subscribe
Explore / Auto-Company
MaxMiksa

Auto-Company

A fully autonomous 'AI company' on your own PC: 14 expert-modeled agents ideate, decide, code, deploy and market 24/7 — driven by Claude Code or Codex CLI, with a local dashboard.

1,325 166 Pythonupdated 1 months ago
agentsorchestration
View on GitHubDispute this mapping →
Curator's take

The maximalist experiment: give 14 role-agents a company charter and let them run around the clock on your hardware. As a living demo of agentic workflows it's genuinely instructive — watch where autonomy compounds and where it wanders. Treat the 'without human intervention' framing as aspiration, NOT audit: unattended agents produce unattended mistakes at 24/7 speed, token bills to match, and there's NO license file at review time — check before building on it.

Mapped by ShipWithAI editors · links verified
README.md

Auto Company

A fully autonomous AI company running 24/7 [中文说明]

Powered by Agentic Workflows, this project orchestrates 14 Autonomous AI Agents, each modeled after world-class experts in their domain. They ideate products, make decisions, write code, deploy, and market - without human intervention.

Powered by Claude Code (default) and Codex CLI on macOS + Windows/WSL, with a local dashboard on both hosts.

macOS Windows WSL Codex CLI Claude Code License: MIT

Dashboard Preview

Auto Company Dashboard

What Is This?

You start a loop. The AI team wakes up, reads shared consensus memory, decides what to do, forms a 3-5 person squad, executes, updates consensus memory, then sleeps briefly. Then it repeats.

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 (3-5 agents)
        │   ├── executes: research, coding, deploy, marketing
        │   └── updates memories/consensus.md (handoff baton)
        ├── failure handling: rate-limit wait / circuit breaker / consensus rollback
        └── sleep -> next cycle

Each cycle is an independent CLI call. memories/consensus.md is the only cross-cycle state.

Where To Start (By Platform)

  • Windows users: start from [Wind

Continue your stack

What teams reach for next — and why each earns a place beside Auto-Company. Ranked by curator confidence.