OpenRig
← All of OpenRig 0.7.16

ChangedOpenRig 0.7.16

Choosing the built-in standard or open policy for a seat now keeps the team's default allowances, so it no longer brings more permission prompts than choosing nothing.

A seat whose effective policy is the built-in standard or open keeps the team launch default, as a seat with no policy does. Any recorded policy used to turn the team default off, so choosing standard brought more prompts than choosing nothing: ordinary rig reads, git reads and tests all asked. The member's policy decides over the rig's. An explicit seat permission choice, a Codex envelope or named Codex profile, a Claude seat's own rules, none, locked, custom, auto and yolo, and kernel, Pi and terminal seats keep their meaning. This keeps the team default; it doesn't apply the whole policy, and a seat that keeps it can still ask before the project's own commands (see Known limits). The Claude team default includes ask rules for lifecycle commands such as rig up and rig down. The Codex team default does not add equivalent per-command ask rules; native settings and explicit permission choices still apply. The launch plan now says whether a seat gets the team default's allowances, instead of a bare launch_posture=floor. OpenRig can't see rules applied in project or user native settings files; those seats keep the team default alongside them, and keeping it doesn't loosen those rules.

Pull request
#3230