What problem it solves

Single-session agents depend on people to start work, block during long-running jobs, share one context, and stop when a machine sleeps. Companies need agents that can run continuously, coordinate parallel work, retain state across sessions, and integrate with the tools and approval processes used by their teams.

Key features

• Event-driven agent execution — Schedules, signed webhooks, connector events, App events, and merged change requests can start agents without someone at the keyboard. Code filters can discard event noise before a model runs.

  Source: README

• Parallel work and agent swarms — Sessions can hand work to background agents, run workflows that coordinate multiple agents, and exchange messages. Each child session reports its result independently.

  Source: README

• Persistent state and long-running work — Each session has its own cloud computer, while state persists across the git repo, Drive, `/workspace`, and the session record. When a context fills, an agent can search its complete session record for the lines it needs.

  Source: README

• Company configuration as code — Agents, skills, rules, connectors, and context are stored as files in a git repository. The `kortix.yaml` configuration declares the system, making its configuration versioned and reviewable.

  Source: README

• Team access and governed changes — Team members can share agents and company context, while roles, groups, per-resource permissions, and approval rules govern access. Changes reaching `main` pass through a change request that a person approves.

  Source: README, apps

Quick start

Copied verbatim from the project's README.

# 1 · Install the CLI
curl -fsSL https://kortix.com/install | bash

# 2 · Scaffold a project: kortix.yaml plus your agents, skills and runtime config
kortix init

# 3 · Ship it: push the repo and bring the whole thing live in the cloud
kortix ship

kortix sessions new --prompt "Summarize this week's commits and open a change request"
kortix cr ls          # review what an agent proposes, merge to keep it
kortix chat           # talk to a session's agent from your terminal

Who it may suit

This may suit engineering, operations, and platform teams that want event-driven agents, shared company context, and versioned agent configuration. It may also suit organizations that need to run an agent harness in their own infrastructure.

Topics to discuss

• Which event sources should be included in the first production workflow?

• How should shared company memory be structured across agents and teams?

• Which approval rules should be required before agents change production code?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/kortix-ai/CompanyOS#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.