Orgus
Sign inGet started
Menu

The control room for AI-assisted development

Autonomy, under control.

Every Claude Code session and agent, live. Approvals in one inbox. Missions through to landed changes.

Get startedSee the product

Agents run on your machines, on Windows, macOS and Linux. The console runs in your browser.

The Orgus console on demo data. On a wide screen, the Overview: what needs you, live sessions, running agents, pipelines and machines, the orchestration flow from projects through agents to delivery and environments, and the live activity. On a phone, the phone app Inbox with requests waiting for Allow or Deny.The Orgus console on demo data. On a wide screen, the Overview: what needs you, live sessions, running agents, pipelines and machines, the orchestration flow from projects through agents to delivery and environments, and the live activity. On a phone, the phone app Inbox with requests waiting for Allow or Deny.

Works with

  • Claude Code Sessions, subagents and workflows
  • Codex Sessions and launches beside Claude Code
  • ACP agents Cursor CLI, OpenCode, goose and more
  • Git Checkouts, worktrees and landing queues
  • GitHub, Google, Microsoft Sign-in under your rules
  • Slack and Teams Approvals and alerts
  • Web Push Approve and deny from your phone
  • MCP Agents operate Orgus through one audited API

The product

Run many agents at once, and stay calm

Seen, governed, delivered and paid for, from one console.

Live

Every agent, on every machine, in one view

Sessions, subagents and workflows across Windows, macOS and Linux, on one timeline.

  • One lane per agent, by session and project
  • State, model, tokens and cost on every session
  • Read-only: nothing you watch is changed
Agents and workflows: running agents, workflows and finished runs, then a timeline with one lane per subagent and workflow phase, grouped by session.Agents and workflows: running agents, workflows and finished runs, then a timeline with one lane per subagent and workflow phase, grouped by session.

Needs you

One inbox for every approval and question

Policy asks a person before a risky step, with the exact command or diff.

  • Ordered by deadline and risk
  • Allow once, for the session, or make it a rule
  • Unanswered requests are denied when they expire
The Inbox: requests waiting with their risk and time left, and the open request with its session, project, machine, the diff and Allow once, Allow for session and Deny.The Inbox: requests waiting with their risk and time left, and the open request with its session, project, machine, the diff and Allow once, Allow for session and Deny.

Delivery

From mission to landed change

Each project's landing queue verifies, rebases and pushes one change at a time.

  • Backlog, missions and review in one place
  • Queued, verifying, pushing, landed, with retries
  • Environments with deploy, freeze windows and rollback
Pipelines: changes in flight, recent results and time to land, then the landing queue with one change pushing, three verifying and three queued.Pipelines: changes in flight, recent results and time to land, then the landing queue with one change pushing, three verifying and three queued.

Cost

Know what every mission costs

Usage costed against a versioned price table, by mission, project, model and day.

  • Budgets with forecasts and hard limits
  • Runaway sessions flagged as they happen
  • Cost per personPlanned
Spend: month to date against the budget with a forecast line, today and cache hit, and three budgets, one near its limit.Spend: month to date against the budget with a forecast line, today and cache hit, and three budgets, one near its limit.

Fleet

Every machine, its load and its agent

Each machine dials out with its own key and keeps limits the server cannot raise.

  • CPU, memory and live sessions per machine
  • Agent updates in rings, canary first
  • A minimum agent version, enforced
Machines: two of three online with their CPU and memory, the sessions each one runs, and an agent update soaking on a canary machine.Machines: two of three online with their CPU and memory, the sessions each one runs, and an agent update soaking on a canary machine.

Anywhere

Approve from your phone

The phone app installs from the console. A decision made offline is sent when you reconnect.

  • Web Push, Slack and Teams, with quiet hours
  • A daily digest for everything that can wait
The Orgus phone app: the Inbox with a medium-risk edit and a package install, each with Deny and Allow once.The Orgus phone app: the Inbox with a medium-risk edit and a package install, each with Deny and Allow once.

Idea to landed

One accountable path from backlog to landed

Each stage has an owner, a state and a record.

  1. Backlog

    Epics, stories, defects and chores, each with an owner.

  2. Mission

    A goal for an agent, on the machine you choose.

  3. Sessions

    Every session, subagent and workflow, live.

  4. Review

    Policy asks a person before a risky step.

  5. Landing queue

    Verified, rebased and pushed, one change at a time.

  6. Deploy

    Preview, staging and a protected production, with rollback.

Security

Security you can check

Read-only where it watches, signed where it acts, recorded everywhere. What is not built yet is marked planned.

Read the security model

  • Watching is read-only

    Watching writes nothing into your repositories. Orgus changes one only when you ask.

  • What the hub stores

    Session state, machines, policy, budgets, missions and the audit log stay in your hub. Nothing is sent to us.

  • Every machine has its own key

    Each machine makes an Ed25519 key pair and proves it on every connection. The private key never leaves the machine; a copied machine secret alone is refused.

  • Signed, expiring commands

    Every command to a machine is signed, sequenced, single-use, bound to that connection and expires after 30 seconds.

  • Hash-chained audit log

    Who, what, where, when and the result, for every action. Each entry carries the sha256 of the one before; orgus audit verify finds the first broken line offline.

  • Machines dial out, and keep their own limits

    One outbound connection, so no open port. The owner can deny any action locally, and nothing the server sends can raise that ceiling.

Get started

Up and running in three steps.

  1. Sign in

    With Google, Microsoft or GitHub.

  2. Add a machine

    One download for Windows, macOS or Linux, with no runtime to install. Approve it in the console.

  3. Start a mission

    Choose a project and a goal. Its sessions show up live.

Get started

Latest: v0.2.0.All changes