The ORION agent
An AI agent that asks
before it touches production.
ORION is the autonomous coding and operations agent inside ORVYN. It plans each mission, acts with real tools, pauses for approval where you require it, and proves the result before it reports back.
Mission lifecycle
From a sentence to a verified result.
Every mission follows the same visible path, so you always know what ORION is doing and why.
- 01
Plan
ORION restates the goal, inspects the code or system, and writes a step-by-step plan you can read before anything changes.
- 02
Act
It edits files, runs commands, opens server sessions or drives a browser — each tool call shown live in the run log.
- 03
Ask
Steps that cross a boundary you set — a production restart, a deploy, a secret — pause for your approval.
- 04
Verify
Tests, health checks, screenshots and diffs confirm the outcome. Failures send ORION back to fix, not to report.
- 05
Report
A summary of what changed, how it was verified and what needs your review, with follow-ups as separate missions.
Modes
Tell ORION what kind of work it is.
A mode sets ORION’s defaults — which tools it reaches for first and how it verifies. Auto picks per step.
Auto
ORION chooses the approach for each step. The right default for most missions.
Code
Repository work: features, refactors, bug fixes and tests, delivered as reviewable diffs.
Server
Diagnose and operate connected machines: logs, services, containers and health checks.
Research
Read docs, code and the web, compare options and return a written recommendation.
Deploy
Ship a change through your pipeline and confirm it is healthy afterwards.
Automate
Turn a repeatable mission into a scheduled or triggered automation.
Many missions at once
A queue you can scan in five seconds.
Missions run side by side, locally or on cloud workers. The list tells you which need a decision, which are blocked and which are done.
Needs approval and blocked states surface firstProgress by step, not by guessworkLocal or cloud execution per mission
Autonomy levels
Decide how much rope ORION gets.
Autonomy is set per workspace or per mission, and you can change it mid-mission.
| Level | Read files | Edit workspace | Run commands | Production actions |
|---|---|---|---|---|
| Ask | Ask | Ask | Ask | Ask |
| Auto Read | Included | Ask | Ask | Ask |
| Auto Workspace | Included | Included | Included | Ask |
| Full Access | Included | Included | Included | Policy |
“Policy” means organization rules still apply: admins can require approval for deploys, restarts or secret use regardless of the mission’s level.
Self-correction
When a check fails, ORION keeps going.
A red test is information, not an ending. ORION reads the failure, forms a new hypothesis and tries again — within the limits you set.
Retry with a reason
Each attempt states what changed since the last one, so loops are visible and easy to stop.
Bounded by budget
Token budgets and step limits keep a stuck mission from running forever. You get a clear “blocked” with the evidence.
Knows when to ask
Ambiguous requirements or risky trade-offs become a question to you, not a guess.
Questions
About the ORION agent
What is ORION?
ORION is the AI agent inside ORVYN. It turns a goal into a mission, uses tools such as the editor, terminal, Cloud Browser, Live Desktop and connected servers, and verifies its work before reporting.
Can ORION make changes to production without me?
Only if you allow it. Autonomy levels and organization policies decide which actions need approval. Production restarts, deploys and secret use can always be set to require a human.
How does ORION verify its work?
It runs the checks that prove the goal: tests, builds, health endpoints, browser checks at several widths, screenshots and diffs. The evidence is attached to the mission report.
Can I stop or take over a mission?
Yes. Every mission has Stop, and terminal, browser and desktop sessions have a take-over control. ORION pauses immediately and resumes from where you leave it.
Can ORION run several missions at the same time?
Yes. Missions run in parallel locally or on isolated cloud workers, and the Missions list shows which ones need you.
Stop prompting.
Start delegating.
Give ORVYN the goal and stay focused on what matters.