OpenRig
← All of OpenRig 0.7.16

AddedOpenRig 0.7.16

Each Codex seat can have its own filesystem rules (read, write and deny) through codex_permissions; enforcement hasn't yet been checked with a real Codex seat. A community contribution.

Per-seat Codex filesystem policies: codex_permissions has an opt-in filesystem form with native read, write and deny rules for that seat's own invocation, carried through managed launch, resume, restore and rebuild. A concrete conflict in the seat's effective Codex configuration stops the launch and names a remedy; a configuration that can't be read keeps the authored invocation and reports "policy not verified". The configuration read and the start aren't atomic. Codex enforces the rules. A seat's resume command in rig ps and node detail carries the policy's flags, but not yet its model and effort. When this release was tested, enforcement wasn't checked with a real Codex seat, and neither were a manual resume with that command nor two seats keeping their policies apart.

Pull requests
#3108, #3239
Contributed by
@Kayhusk