AG COMP is a system where one founder runs a real company with a team of AI employees built on Claude Code. Each seat has its own job, memory, and permissions, and they hand work to each other through a shared company brain. The founder approves anything that leaves the building.
See how it worksAG COMP isn't a demo. Every task, decision, and lesson our AI team produces is written to a version-controlled knowledge base. These are the numbers as of October 2026.
Small, boring rules that let AI employees work without the founder relaying every message.
A chief of staff routes requests. Leads own strategy and implementation for development and design. A separate QA seat verifies work it didn't do. Specialists are called on demand for one task.
Briefs, run reports, decisions, and lessons live in plain Markdown in Git. Seats search it for what they need instead of reading everything, and keep a small personal memory of their own craft.
Work moves queued → claimed → working → verifying → done. A task can't close until its output, verification output, and commit actually exist.
Reading and reversible local work proceed automatically. Sending messages, publishing, payments, and account changes stop and wait for the founder's approval.
The founder states a goal. The team handles the hand-offs.
Claude Code is the core of the office. Planning, development, design judgment, and the founder-facing chief of staff all run on Claude, and Claude reviews the work it hands over.
# example session $ ./office.sh ledger view T-…-landing-page working dev lead R1 T-…-study-qa verifying qa R1 T-…-daily-push done dev lead R3 approved $ bash scripts/check.sh harness checks ............ passed
Internal tools the AI staff designed, built, tested, and deployed for the founder. They prove the system on real work before we offer it to others.
A login-protected study app with an offline queue, wrong-answer review, and data synced from a tutoring seat.
A personal daily planner that combines a read-only calendar feed with tasks and notes, behind a single access key.
A dedicated seat plans, scripts, and produces videos for an automated channel, one episode per call.
Dead-automation sensors, a status board, session recovery, and a commit guard that keeps seats from committing each other's work.
Next, we're packaging the office so other solo founders can set it up: seat definitions, the brain layout, the ledger, and the approval rules. We are also building evaluations to measure how well AI seats route, verify, and hand off work.