Repository navigation
Conversation
…over it Where this plugin is seated, a plugin a person installs no longer answers more permissively than any deny on tool.check, an ask a settings rule or a classic hook decided, or a variable managed settings set in env. The lines an organization's plugins log, this one's included, continue past the user tier.
The hold of a classic hook's ask is read off a field the published engine does not carry yet, so it leaves this change and follows by itself. What stays needs no new engine: any deny, an ask a settings rule decided, the organization's own log lines, and the variables managed env sets.
poteat
enabled auto-merge (squash)
October 3, 2026 07:15
This was referenced Oct 3, 2026
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.
Summary
Needs no new engine: it reads nothing the published one does not carry.
Notes
tool.check, any denytool.check, an ask ruleui.log(new)prependorappendlogs, this one's included, continues past the user tier. A user hook that heard this plugin's own notice ran inside itstool.checkhook, and the engine leaves a hook out of whatever is raised from inside it: the notice was a way round the hold, deny rules includedenv.set(new)env(its name in any case) is pinned: a user-tier caller is refused by name, setting or unsetting; any other caller continues past the user tier. With no policy to read every variable counts as pinned. Its.catchfails closedallowModsToOverrideDenyRulescovers all that holds ontool.check. It does not unpinenv$.ui.logand$.env.setof any plugin now runs a chain where this plugin is seated; anenv.setwaits on the policy readPermissionRequesthook of the person's answers it (allowManagedHooksOnlyis the control). A command hook decides only if its command runs: a variable its spawn depends on (PATH,CLAUDE_CODE_SHELL_PREFIX) that managedenvdoes not set is a person's to change. The README says eachTest Plan
claude plugin test mods/sec-defaulton the published 2.1.288: 86 pass (57 before).env.setcase.env.set's.catch: only a hook that overruns its budget reaches it, and the kit cannot shorten a budget.tsc -p mods/tsconfig.json: clean.claude plugin validate: passes.