v0.1.0

RoboCo v0.1.0 — first public release

RoboCo is a virtual software company: 20 AI agents and one human — you, the CEO.
You hand work in at the top; the organization carries it through planning, building, review, and documentation, then brings it back for your sign-off. You act at the two ends; the agents fill in everything between.

What holds it together is structure, not a clever prompt — everything is a task, no task moves without acceptance criteria, and every task walks the same role-gated lifecycle: built, QA'd, documented, PM-reviewed, approved.

⚠️ This is v0 — early-stage homelab software. Expect rough edges, breaking changes, and an unstable schema. Run it on a trusted private network; do not expose it to the public internet as-is.

What's inside

• A real organization — CEO → Intake → Board (Product Owner · Head of Marketing · Auditor) → Main PM → three delivery cells (Backend · Frontend · UX/UI): 20 agents, formal communication, and a silent Auditor watching the whole time.
• The Task Assistant — chat with an agent that reads your actual codebase, interviews you, and drafts a well-formed task (objective, per-cell breakdown, acceptance criteria) ready to launch. RoboCo built this feature itself.
• A gated task lifecycle — backlog → pending → in progress → QA → documentation → PM review → CEO approval → done, every transition enforced by role.
• Real git, real PRs — each agent works in its own clone; cells open PRs into the Main PM's integration branch; only the CEO ever merges to master.
• Two human moments — approve the spec to start, approve the final PR to ship. The company runs itself in between.
• One cockpit — a Next.js control panel (tasks, Kanban, agents, journals, notifications, live metrics, the Task Assistant) behind a single nginx entry point.
• Grounded agents — a piragi + pgvector knowledge base, local inference via Ollama, cloud via Claude.

See it work

The walkthrough in docs/how-to.md follows RoboCo building one of its own features — the Task Assistant — across all three cells, failing and re-running its own QA, and opening the real pull request. RoboCo builds RoboCo.

Run it

Clone and docker compose up (builds locally), or pull the published images:

• GHCR: ghcr.io/rennf93/roboco-* — orchestrator, panel, agent-base, and the eight agent images, at 0.1.0 / latest
• Docker Hub: renzof93/roboco-*, at 0.1.0 / latest

Setup, configuration, and the security model are in the README.

License

AGPL-3.0. Contributions welcome under the CLA.

---

Full Changelog: https://github.com/rennf93/roboco/commits/v0.1.0