Repository navigation
Add disabled Always-On action policy foundation - #521
Open
leprachuan wants to merge 1 commit into
Open
leprachuan wants to merge 1 commit into
leprachuan wants to merge 1 commit into
Conversation
This was referenced Oct 4, 2026
leprachuan
marked this pull request as ready for review
October 4, 2026 14:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Always-On agents need scoped server-owned permissions before autonomous work can be enabled. This adds canonical action fingerprints, literal agent/operation/host/resource allow/ask/deny rules, deny precedence, atomic JSON persistence, and creation/revocation audit metadata. Unknown and opaque shell/python/browser/delegation actions still ask even with a matching allow rule. Defaults disabled; no execution paths or current chat behavior change.
Validation: 23 focused tests passed on dev 192.168.1.100, covering mismatched scope, path traversal/boundaries, fingerprint binding, corrupt schema, invalid feature flags, revocation, and failed atomic writes.
Tracks #519 and #520. The execution-surface map records SDK built-ins and runtime boundaries Stage 2 must enforce before enablement. Remaining: shared approvals and authorized APIs, execution wiring, inherited delegation constraints, symlink-safe adapters, process-safe policy coordination, and all three UI clients.