# Run the whole company from one open-source repo

> A company runs on AI agents once its roles, memory and permissions live in one repo a person approves changes to. Kortix is the open-source CompanyOS: your agents, their skills, your company memory, and every connector in one git repo you own, with the agents working on real cloud computers.

URL: https://companyrunbyagents.com/

For teams past the demo

**The open-source CompanyOS**

`kortix.yaml`

```yaml
# Engineering
eng-triage:
  description: Triages every new GitHub issue.
  prompt_file: agents/engineering/triage.md
  tools: [read, grep, glob, web_search]
  connectors: [github, kortix_slack]
```

Source: https://kortix.com

Thousands of agents in parallel on one config, each on its own cloud computer.

[Try Kortix](https://kortix.com) · [See the loop](https://companyrunbyagents.com/#use-cases)

Open source · Merge is default-deny for agents · One repo you own

## How the loop hands work back

Three artifacts a person reviews: a change request, a scheduled audit and a drafted reply.

### Engineering: A fix arrives as a change request.

The agent reproduces a failing export on its own cloud computer, patches it and opens the change for review.

Output: `change-requests/fix-export-timeout.diff`

```diff
 agents/reporting.md
-Export runs every hour.
+Export runs at 06:00 and retries twice.
```

+1 -1

Opened by eng-triage, waits for a person

### Operations: The Monday audit runs on a schedule.

A cron trigger runs the audit; when it finds a gap it opens a change request instead of fixing it quietly.

Output: `schedules/monday-audit.md`

- trigger: cron 09:00 Monday
- scope: billing and access
- flags: 2
- next: one change request

Ran once, returned two items

### Support: The reply is drafted from company memory.

The agent writes the answer from the account's memory files and leaves it for a person to send.

Output: `drafts/northwind-invoice-reply.md`

| Field | Value |
| --- | --- |
| Account | Northwind |
| Ask | Copy of the March invoice |
| Draft | Ready for review |

Nothing sent without a person

## Two ways to put agents to work

More agents on more machines is still the demo; Kortix runs a company repo you review, OpenClaw an assistant on your own machine.

| | Kortix (recommended) | OpenClaw |
| --- | --- | --- |
| What it is | A company repo you own: agents, skills, memory, connectors. | An AI assistant you message from chat apps. |
| Where agents run | On their own cloud computers. | On the machine where you install it. |
| Who approves a change | A person merges a change request; merge is default-deny for agents. | The owner approves the big calls. |
| Memory | Company memory in the git repo you own. | Markdown memory files per agent. |
| Self-host | Self-host is free. | No hosted tier; it runs on your machine. |
| Open source | Yes | Yes |

Sources: OpenClaw's [own page](https://openclaw.ai), and an owner's [published seven-agent experiment running OpenClaw](https://hellonunc.com/blog/posts/company-run-by-ai-agents/), with a CEO, a CTO and five staff on one 4GB VPS. Both read 4 November 2026. Kortix's manifest is quoted from kortix.com.

**20,000+** GitHub stars

## Open source, and yours to run

[Read the source](https://github.com/kortix-ai/CompanyOS) · [What lives in the repo](https://companyrunbyagents.com/company-as-code)

## What buyers ask before moving the company over

### Can AI agents run a business?

Yes, if a person keeps the last word. Agents can run a company's work when roles, memory and permissions sit in one repo, and a person reviews every change. An owner's [seven-agent experiment](https://hellonunc.com/blog/posts/company-run-by-ai-agents/) left half the agents' own files unupdated and two agents unnamed inside a week.

### Do I need to know git to run a company this way?

No. You work in Kortix, and an agent opens a change request for anything it wants to change. The repo is the record, not the interface.

### How do I correct an agent that has the wrong role?

A role is one `agents.<name>` block in `kortix.yaml`, with its prompt file, model and permission. An edit an agent makes to the block opens a change request that a person merges; an edit you make from the dashboard can commit straight to the default branch.

## Hand the first outcome to an agent this week

One role, one repo, one change request a person reviews. Add the next role when the loop holds.

[Try Kortix](https://kortix.com)