Set what Ysra may do without asking in Code threads, for your whole account or one repository — every setting, its choices and default, and a policy to start with.

On this page

An autonomy policy is the set of rules for what Ysra may do on its own in a Code thread, what it must ask about first, and what it may never do. Change it when you want Ysra to go further without stopping (open a pull request, run installs) or to hold back more. Safe defaults apply until a policy is saved. This page lists every setting; where to find them is on Settings.

The policy is set in the web app, Settings → General, under Defaults. Code threads in the desktop app and the CLI read it from there.

How the settings combine#

Repository settings override the account's only for the settings they set; everything else follows the account. The repository's checks always run, and no setting turns them off.

How policies combine#

Level Applies to Detail
Defaults Every repository The account's policy
For one repository That repository only Each setting offers Use the account’s setting; a setting left on it keeps following the account, even when the account changes later
In effect What a thread runs under Shows each choice, marked set here or from the account

Only the settings under Running work and Delivering work can be set for one repository.

YOUR SETTINGS COMBINED EACH SESSION Account policy Repository override only the fields it sets Effective policy Session contract fixed for the whole session at start
The account's policy and a repository's overrides combine into the policy in effect, fixed for a session when it starts.

Settings#

Details under a setting in the app shows the same list.

Running work#

Setting Choices Default
Autonomy — how much is done before stopping for you. What happens to the result is under Delivering work. Only suggest changes, Write the code, then wait for review, Open a draft pull request, Merge when the checks pass Write the code, then wait for review
Downloading dependencies — whether packages may be fetched from the network while installing. Never, Ask first, Allow Ask first
Running install commands — whether commands that install dependencies may run. Never, Ask first, Allow Ask first

Delivering work#

Setting Choices Default
When a change passes its checks Keep it for you to review, Push a branch, Open a draft pull request, Merge it Keep it for you to review
When a change’s checks fail Keep it for you to review, Open a draft pull request that lists what’s still open Keep it for you to review

Always on#

Setting Value
Checks always run The repository's tests run before a change is reported as done. Can't be turned off

Some choices aren’t available yet

Not every choice does what its name suggests today. In particular, the Autonomy choice Merge when the checks pass doesn't merge anything. Choices that can't be picked yet aren't shown as buttons; Details lists them under Not available yet. Treat the Settings page as the source of truth, not this table.

A policy for a first rollout#

Start conservative and widen one setting at a time:

Setting Start with
Autonomy Write the code, then wait for review
Running install commands Ask first
Downloading dependencies Ask first
When a change passes its checks Keep it for you to review
When a change does not pass its checks Keep it for you to review

Who can change it#

Owners and admins of an organisation. For anyone else the controls are turned off: "Only an owner or an admin of this organisation can change that." See Members and roles.

YsraDocs