Start a chat
- From the Orion page. Open Orion, pick Orion Code from the agent picker in the box, and send. Choose a project and a branch, then click Start. You can also click New Orion Code chat in the sidebar.
- From a project. Open Orion in the project’s drawer and choose Agent mode. Agent mode lets Orion change files and act. Ask mode only answers questions.
The sandbox
Orion Code works in a sandbox: a separate environment that holds a copy of the project, including your unsaved changes and Orion’s own edits. Commands run there. In the sandbox, Orion can:- build, test and lint the project, and install packages
- run a script to check something
- use the
datazoneCLI and the Datazone REST API, with your permissions - wait for pipeline and extract runs and Studio App builds to finish
- open a Studio App in a browser to check it
Waiting for runs
Some steps depend on a run that is still going. Orion then waits instead of polling. The chat shows Orion is waiting for 2 runs to finish and will continue by itself. When the runs end, the chat continues on its own with a new message that says how they ended. You can close the tab in the meantime.When there is no sandbox
Some deployments have no sandbox. The workspace panel shows Sandbox off, and Orion works only with files:- It cannot run commands, such as installs, builds or tests.
- It cannot build or preview a Studio App, run a pipeline or an extract, or use the CLI or the REST API.
- It can edit project files, then land them with Deploy or Open pull request.
- It checks its work by reading the code. It tells you which steps are left for you in the UI, and says plainly what it did not build or run.
On a self-hosted installation, the sandbox is switched on or off in the deployment configuration.
Pending changes, deploy and pull requests
Orion’s edits are proposals until you land them. The workspace panel lists the Changed files, and each one opens a diff against the branch. Nothing is committed until you act:- Deploy commits the pending changes to the branch the chat is on, and deploys it. You confirm first. The dialog says how many files will be committed and to which branch.
- Open pull request commits the changes to a new branch of their own, and opens a pull request into the branch you pick under Into. The chat then continues on the new branch.
Permission levels
The Permission control in the input sets how far Orion goes without asking.
When Orion asks for approval, you can choose Allow once, Allow all in this chat or Deny.
Orion Code starts on Manual. In a project’s drawer, the level you choose is remembered in this browser.
Model
Next to the permission control, a button shows Default (model name). That is the organisation’s default model for Orion Code. Click it to run your questions on another chat model. The choice applies to your questions until you reload the page. Models come from the model accounts of your organisation.Ask, stop and queue
An Orion Code run keeps going on the server. If you close the tab or lose the connection, the answer carries on. When you reopen the chat, the run appears where it was.- Stop ends the current answer. The answer shows Stopped. Its partial answer is kept.
- Queue: type while Orion is still answering. Your message waits, marked Queued — starts when the current answer finishes. Click Cancel to remove it.
- Connection lost, reconnecting… shows while the page reconnects. Nothing is lost.
- If the platform restarts during a run, the answer shows The run was interrupted before it finished. Ask Orion to continue. Ask it to continue, and it picks up from the partial answer.
- A queued message that is cancelled before it starts shows Cancelled before it started.