SARION

Permissions, recovery and credits

The four permission modes, what happens when a change is uncertain, and how the command line shares your account, plan and credits with the web app.

Where to find it Terminal, --permission-mode

The four permission modes

Choose a mode with --permission-mode. The mode decides what SARION may do in your folder.

  • read-only: SARION may read the files you share. It may not run programs or change anything in your workspace.
  • workspace-write: SARION may apply checked patches to your files. Running a program still needs your approval.
  • approval-required: you review the exact plan of each effect before it happens.
  • trusted-automation: for unattended runs only. It requires a protected policy file that you control, and a denial in that policy always wins.

There is no --yes option. A script cannot approve things on its own: without a person to ask, it must name the mode and give --share-context explicitly. Native Windows refuses programs and Git changes in every mode; use WSL2.

Safe by default

Start with read-only. On Linux and macOS, programs run inside a sandbox, and if the sandbox cannot start, the program is not run without it. sarion sandbox doctor shows whether this machine can contain programs. Files that look like secrets, ignored files and links are left out of what is shared, but that is a safety net and not permission to work in a folder of secrets.

When something is uncertain

If a run stops while a change may or may not have happened (for example the connection dropped), SARION marks the effect as uncertain instead of guessing. A timeout is not proof that nothing changed.

  1. Run sarion recover SESSION_ID to inspect what is known.
  2. Check your files with your usual tools (git status, git diff).
  3. Only then decide: continue, restore a checkpoint with sarion checkpoint restore ID, or give up on one command with sarion recover SESSION_ID --abandon COMMAND_ID.

Do not delete journals, bypass recovery or run the same command again blindly. Keep receipts and checkpoints when you update, sign out or move the program.

Same account, same credits

The command line is another way into your own account. It uses the same plan and the same credit as the web app, chat and voice, so one balance covers all of them. A request to SARION (ask, agent, chat) uses credit like a chat message does, and bigger requests use more.

  • sarion usage shows the usage and balance that your account reports. It is the server's figure, not an invoice.
  • The web app shows the same balance under Usage & Balance. See Billing and credits.
  • Missing credit, a plan that is not active or a limit set by your account can refuse a request. Fix it in the web app: add capacity or switch on Automatic top-up.
  • Your command line activity is included when you use Download my data. See Your data.

Common questions

Can it change my files without asking?

Only in workspace-write mode for checked patches, and only after you chose that mode. It still asks before it runs a program.

Does using it cost more than the web app?

It uses your credit the same way. There is no separate price.

Where do I add credit?

In the web app: Usage & Balance, then Get more capacity.