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
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.
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.
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.
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.
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.
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.
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.
full_auto
Runs the commands, reads each result, diagnoses errors and retries on its own until the goal is verified.
safe_auto
Runs read-only and standard commands automatically, then pauses with an inline gate before sudo or a destructive command.
confirm_each
Pauses before every step, so you approve each command before it touches the shell.
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.
One setting, changed per task
The plan, the approvals and the log look the same whichever engine is selected.
ORCAOS is a native GTK3 application for the Linux desktop. Clone the repository, run the installer, then start it from any terminal.
$ 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:
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.
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.