• Loading…

Modes and permissions

How much SoreQen asks before it acts, what it always asks about, what it never does, and the ceiling a workspace can set.

The four modes

ModeWhat it does
PlanReads and plans. Changes nothing.
ManualAsks before every edit and command.
AutoAsks only before changes that can't be undone.
BypassNever asks. Blocked actions stay blocked.

Auto is the default. Change it with /mode, with --mode when you start, or from the menu under the message box in the desktop app:

/mode plan
soreqen --mode manual

What Auto asks about

Auto works on the rule that a checkpoint can undo an edit, so edits don't need your yes. It stops for what a checkpoint cannot undo:

  • deleting files recursively and by force (rm -rf, and the Windows equivalents)
  • dropping or emptying database tables
  • git push, git reset --hard and git clean -f
  • anything run with sudo
  • publishing a package (npm, pnpm or yarn publish)

Manual asks before all of these and every other change. Bypass asks before none of them.

What it never does

Some commands are refused in every mode, Bypass included, because they have no use inside a project: reaching the Docker socket, writing kernel parameters, reading or editing system password files, formatting a disk, raw device writes, deleting the filesystem root, fork bombs, piping a downloaded script straight into a shell, and running encoded PowerShell.

Permission tiers

A tier is a ceiling for a workspace: the most a session there may do, whatever the mode. Each mode has a matching tier.

TierThe same limit as
read_onlyPlan
propose_onlyManual
guarded_autonomyAuto
full_autonomyBypass

Set one with --tier (or -t) when you start. When a tier is set, the narrower of the mode and the tier wins: choosing Bypass in a read_only workspace still gives you a read-only session. With no tier set, the mode alone decides. /tier shows the current ceiling.

soreqen --tier read_only