Show your Linux terminal the goal. Let ORCAOS run the steps.

ORCAOS is an autonomous agent for the Linux desktop. Describe the outcome in plain words and it writes the commands, runs them in a real /bin/bash terminal, reads the output, and repairs the usual Linux failures before it reports back.

  • Real /bin/bash terminal
  • Auto, Safe or Manual
  • Open source on GitHub
The ORCAOS desktop window on Zorin OS The ORCAOS native GTK3 window. The top bar carries the ORCAOS name, a distro and resource pill reading Zorin OS 18, CPU 6 percent and 3.2 of 16 GB RAM, a mode switcher set to Safe, and a Ready status dot. The AI Operator pane on the left shows a WHEN goal, a first THEN command that needs sudo, an IF approval gate with Approve, Skip and Stop buttons, and an exit code of 0 in 42 milliseconds. The /bin/bash PTY pane on the right shows the commands running, their output, and a diagnosis of that output. ORCAOS by Orcamatic Zorin OS 18 · CPU 6% · RAM 3.2/16 GB Auto Safe Manual Ready AI Operator safe_auto WHEN Install jq and confirm it is available to cron jobs. 1. THEN $ sudo apt-get install -y jq IF SAFE MODE APPROVAL GATE This command needs sudo. Approve, skip or stop the step. Approve Skip Stop plan paused Exit 0 (42 ms) stdout 214 B · stderr 0 B · step verified Self-heal ready: dpkg lock, PEP 668 /bin/bash pty pid 4821 $ orcaos "install jq and verify it works" [orcaos] goal read: 3 steps planned [orcaos] step 1 paused: safe mode gate $ sudo apt-get install -y jq Reading package lists... Done Building dependency tree... Done Setting up jq (1.7.1-3) ... $ jq --version jq-1.7.1 Output diagnosis stdout matches the plan, stderr is empty. Exit code 0 in 42 ms, so the step is verified. No retry needed. Steps 2 and 3 continue. $ Safe mode · 1 approval · 0 retries GTK3 · /bin/bash PTY · exit 0
Illustration of the ORCAOS window. A goal becomes a plan, the plan runs in a real shell, and anything that needs sudo waits behind the gate that you chose.

WHEN / THEN / IF, for the shell

The rule language that drives ORCA in the browser drives ORCAOS on Linux. The goal you describe is the WHEN. The commands it plans are the THEN steps. The checks, the error handling and the approval gate are the IF.

  1. Describe the outcome, not the commands

    Say what finished looks like: install jq, clear the apt cache, set up a Python virtualenv, fix a broken package. ORCAOS drafts a short plan of shell commands to get there.

  2. Run it in a genuine /bin/bash terminal

    Every step goes through a real pseudo-terminal, so pipes, aliases, prompts and exit codes behave exactly as they do when you type them yourself. No simulated shell, no translation layer.

  3. Read the output, not only the exit code

    After each step ORCAOS inspects stdout and stderr, decides whether the plan actually worked, and states the reason in the planner pane instead of assuming success.

  4. Self-heal the failures Linux keeps producing

    When a step fails for a reason it recognises, ORCAOS diagnoses the failure, adjusts the command, and retries inside the same plan until the goal is verified.

dpkg lockAnother apt process already holds the lock. ORCAOS waits for it or tells you which process owns it instead of retrying blindly.

missing apt cachesPackage lists are stale or absent, so it refreshes them with apt-get update and replays the install that failed.

PEP 668A system Python refuses pip installs, so it moves the work into a virtualenv instead of forcing the install with a broken-packages flag.

permission deniedCommands that need root are escalated to sudo, and in Safe mode that escalation waits for your approval first.

Three autonomy modes. One plan.

The same plan can run three ways. Switch the mode and the approval gate moves with it, so autonomy is a setting you choose rather than a surprise.

Auto

full_auto

Runs the commands, reads each result, diagnoses errors and retries on its own until the goal is verified.

  • Best for long installs and repeatable setup
  • Stops when the plan is done or blocked
  • Every command and result stays in the log

Safe

safe_auto

Runs read-only and standard commands automatically, then pauses with an inline gate before sudo or a destructive command.

  • Approve, Edit or Skip each risky step
  • The recommended way to start
  • Nothing destructive happens without you

Manual

confirm_each

Pauses before every step, so you approve each command before it touches the shell.

  • You read every command first
  • Useful while learning an unfamiliar tool
  • The plan and the log stay identical

Bring your own model, or bring none

ORCAOS keeps the Orcamatic approach: the reasoning is replaceable, and the automation stays inspectable. Point it at a hosted model with a key you own, at a model running on the same machine, or at the built-in engine that needs no network at all.

  • Google Gemini, OpenAI, Anthropic Claude, Groq and OpenRouter with your own API key
  • Local Ollama on 127.0.0.1:11434, so prompts and output never leave the machine
  • The offline ORCAOS Built-in Diagnostic Engine for the standard Linux failure patterns
  • Switch provider per task; the plan keeps the same WHEN / THEN / IF shape
Read the setup notes
AI Engineyour choice

What ORCAOS can think with

One setting, changed per task

  • Google GeminiAPI key
  • OpenAIAPI key
  • Anthropic ClaudeAPI key
  • GroqAPI key
  • OpenRouterAPI key
  • Ollama on this machine127.0.0.1:11434
  • Built-in Diagnostic Engineoffline

The plan, the approvals and the log look the same whichever engine is selected.

Install in one clone

ORCAOS is a native GTK3 application for the Linux desktop. Clone the repository, run the installer, then start it from any terminal.

TerminalZorin OS 18
$ git clone https://github.com/mabk26/ORCAOS.git && cd ORCAOS && chmod +x install.sh && ./install.sh
$ orcaos

On the first run, ORCAOS asks which AI engine to use. The Built-in Diagnostic Engine needs no key and no network.

ORCAOS runs on the desktops Linux users actually keep:

  • Zorin OS, Ubuntu, Linux Mint and Pop!_OS
  • Debian and Kali Linux
  • Fedora and Arch Linux
  • Any GTK3 desktop session with a standard /bin/bash shell

Automation that keeps you in the loop

ORCAOS works on your machine, under your user account, and shows the command before it runs whenever the mode calls for approval. Nothing is hidden in a queue you cannot see, and the actions it takes are the ones written in the plan on screen.

What the gate covers

sudo or root commandApprove, Edit or Skip
Destructive commandGated in Safe
Read-only inspectionRuns automatically
Plan and outputOn this machine

Give the terminal the goal. Keep the judgment.

Install ORCAOS on your Linux desktop, start in Safe mode, and hand it the setup steps you repeat every time you touch a new machine.

ORCAOS is open source and installs from its GitHub repository. ORCA, the browser extension, is the other half of the Orcamatic lineup.