How do I start my first ORVYN mission?

Open a project, pick an autonomy level such as Ask, then describe the outcome you want in the Home composer and press Ctrl+Enter. ORION shows its plan before it acts.

What should a good mission goal look like?

Describe the outcome and how to check it, for example “Fix the failing checkout tests and verify checkout in the browser.” Outcomes give ORION room to investigate; step-by-step commands do not.

How do I connect a server to ORVYN?

Add it under Servers with its host and user, and store the credential in the Secrets Vault. Missions refer to it by SecretRef.

Where do generated files go?

To Files → Generated in your workspace, where you can preview, download or reuse them.

ORVYN Docs: Missions, Vault, Models & Shortcuts

Getting started

Download ORVYN for Windows or create an account to use cloud workers.
Open a project folder or repository. This becomes your workspace.
Choose an autonomy level. Ask is a good first setting.
Give ORION a goal, for example: Fix the failing checkout tests and verify checkout in the browser.

Missions

A mission is one goal, carried from understanding to a verified result. ORION moves through six phases — Understand, Inspect, Act, Test, Verify, Deliver — and records each step in the run log.

Write goals as outcomes rather than instructions. “Find why staging returns 502 and fix it” gives ORION room to investigate; a list of commands does not.

Several missions can run in parallel, each with its own context and, in the cloud, its own worker.

Autonomy levels

Level	Runs automatically	Asks first
Ask	Nothing	Every action
Auto Read	Reading files, logs and resources	Any change
Auto Workspace	Edits, commands, tests, Browser and Desktop inside the workspace	Anything outside the workspace
Full Access	Connected resources, within granted permissions	Whatever your policy requires

You can Stop a mission or Take Control of a Browser or Desktop session at any time.

Resources and the Secrets Vault

Resources are the things outside your code that missions may use: servers, databases, cloud accounts and MCP tools. Each resource points to its credential through a SecretRef such as vault/staging/ssh.

Secrets are encrypted in your tenant’s vault and decrypted only inside the runtime that opens the connection. The model works with the reference and never receives the plaintext value.

Browser and Desktop

ORION can open a Browser session to verify web apps, and a Desktop session to operate applications visually. The session header always shows who is in control. Use Take Control to drive it yourself and hand it back when you’re done.

Models

With Auto, ORION analyzes each step and routes it to a Fast, Code, Frontend or Premium lane. You can also pin a model for a workspace or a mission. Every lane uses the same ToolGateway and the same verification.

Artifacts

Images, reports, data exports and other generated files are saved to Files → Generated. Each artifact can be previewed, downloaded or used in the project.

MCP integrations

Connect tools such as GitHub, GitLab, Slack, Jira, databases, cloud providers or your own MCP servers. ORION discovers their capabilities and uses them when a mission needs them, subject to your autonomy level.

Automations

An automation is a mission that starts on a schedule or an event — for example every night at 02:00, after each deploy to staging, or when a pull request is opened. Automations use the same permissions, approvals and verification as missions you start by hand, and their results appear in Missions.

Good first automations: a nightly dependency audit that opens a pull request, a staging smoke test after deploys, and a weekly usage report saved as an artifact.

Keyboard shortcuts

Shortcut	Action
`Ctrl` `N`	New mission
`Ctrl` `K`	Search, or edit the selected code with ORION
`Ctrl` `Shift` `P`	Ask ORVYN from anywhere in the app
`Ctrl` `L`	Focus the conversation
`Ctrl` `Enter`	Run the mission

Troubleshooting

A mission says “Blocked”

ORION stops when it needs a decision it should not make alone, or when it runs out of budget. Open the mission: the last message explains what is needed. Answer it, raise the budget, or adjust the plan.

A mission is waiting for approval

The step crossed a boundary set by your autonomy level or an organization policy. Review the command and target, then approve or deny. Denying with a reason lets ORION look for another way.

ORION cannot reach a server

Check the resource in Servers: host, user and SecretRef. Confirm the credential exists in the vault and that your role is allowed to use it in this workspace.

Cloud worker shows offline

The status bar shows whether ORVYN Cloud is connected. If a worker is offline, missions using it pause and resume when it reconnects, or you can move the mission to another worker.

ORVYN docs