Kortix CompanyOS

The open-source CompanyOS: the cloud-native agent harness for companies.

Open Source  ·  Extensible  ·  Multiplayer  ·  Sovereign

Always-on agents that start on events, run in parallel and share one memory of your company.

Build custom agents on pi and ship them from one git repo. Schedules, webhooks, your tools' events and your team's messages start them. My Kortix routes the work, and swarms of agents run it in parallel, each on its own cloud computer with state that persists.

Agents connect to 3,000+ apps, build and host the apps your company needs, and land every change through a review your team approves. Share agents and context across your whole team. Open source, any model, on your infrastructure or ours.

Website · Guide · Cloud · AI Transformation · Manifesto

---

A new kind of system

An agent today is one chat session on one machine. It waits for a person to type. It blocks while a long job runs. Every task it takes on shares one context. It stops when the laptop sleeps. A person can follow only a few such sessions at once, so human attention runs out long before the model does.

Kortix CompanyOS takes the session out of the person's hands. It is a cloud-native agent harness: you write custom agents on pi, an open-source agent harness, and Kortix deploys them to the cloud and supplies everything around the agent loop that one session cannot.

Always on	Compute and state are separate. Every session runs on its own cloud computer. The computer sleeps 15 to 20 minutes after the last turn and wakes on the next message or event, with its full history. State lives in the repo, in Drive, in the session's /workspace and in the session's record.
Event-driven	Triggers start agents from schedules, signed webhooks, connector events, App events and merged change requests. A filter in code drops noise before any model runs. A session subscribes to the events of its own work, and an agent sets its own check-in before it stops.
One agent to talk to	You talk to My Kortix. It answers at once, hands writing, research, code and app work to the agent made for it in a session of its own, and tells you the result. Nothing it hands off blocks the conversation. A follow-up goes to the same agent, with everything that agent already knows.
Swarms	A session hands work off in the background, runs a workflow that coordinates many agents, and messages other sessions. Every child reports back by itself. Thousands of agents run in parallel on one config.
Long horizon	When a context fills, the agent continues in a fresh one and searches the session's full record for the exact lines it needs. Nothing is summarized. A job outlives one turn and one context window.
Scales out	Compute is disposable and state persists, so capacity grows by adding computers, not by growing one. Each new session gets its own computer. A sleeping computer uses no compute.

  You, in the web app             Slack · Teams · email        Events
        │                         threads                      schedules · webhooks
        ▼                              │                       app + connector events
 ┌─────────────┐                       │                       change requests · loops
 │  My Kortix  │ answers at once,      │                              │
 │             │ never blocks          │                       ┌──────┴──────┐
 └──────┬──────┘                       │                       │  Triggers   │ filter in code,
        │ hands off in the background  │                       └──────┬──────┘ then start or wake
        ▼                              ▼                              ▼
 ┌────────────────────────────────────────────────────────────────────────┐
 │ Agent sessions: custom pi agents, each on its own cloud computer       │
 │ hand-offs · workflows · messages between sessions · reports back       │
 └────────────────────────────────────────────────────────────────────────┘
                                     │
                                     │ sleeps when idle, wakes with its full history
                                     ▼
   State that persists: git repo · Drive · /workspace · session record
   What lands on main goes through a change request a person approves

Connect your company's tools once, and every agent and every teammate works with them, with the same skills and the same company memory. Your agents, skills, memory and connectors live in one git repo you own: your whole company as code. Any model, your own keys, on Kortix Cloud, in your VPC or on your own on-prem network.

---

Kortix, end to end

One system, from the message that starts the work to the change that lands it.

This is the beginning of the README. Read the rest at the original. Read the full README ↗