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.
+1 -1
Opened by eng-triage, waits for a person
The open-source CompanyOS
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.
Open source · Merge is default-deny for agents · One repo you own

# Engineeringeng-triage: description: Triages every new GitHub issue. prompt_file: agents/engineering/triage.md tools: [read, grep, glob, web_search] connectors: [github, kortix_slack]Three artifacts a person reviews: a change request, a scheduled audit and a drafted reply.
Engineering
The agent reproduces a failing export on its own cloud computer, patches it and opens the change for review.
+1 -1
Opened by eng-triage, waits for a person
Operations
A cron trigger runs the audit; when it finds a gap it opens a change request instead of fixing it quietly.
Ran once, returned two items
Support
The agent writes the answer from the account's memory files and leaves it for a person to send.
| Field | Value |
|---|---|
| Account | Northwind |
| Ask | Copy of the March invoice |
| Draft | Ready for review |
Nothing sent without a person
More agents on more machines is still the demo; Kortix runs a company repo you review, OpenClaw an assistant on your own machine.
Sources: OpenClaw's own page, and an owner's published seven-agent experiment running OpenClaw, 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
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 left half the agents' own files unupdated and two agents unnamed inside a week.
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.
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.
One role, one repo, one change request a person reviews. Add the next role when the loop holds.