feat: add tool permission guard#2463
Merged
hsluoyz merged 1 commit intoJul 22, 2026
Merged
Conversation
This was referenced Jul 16, 2026
lulululu-debug
force-pushed
the
feat/tool-permission-guard
branch
3 times, most recently
from
July 22, 2026 02:16
5e09c65 to
3151607
Compare
lulululu-debug
force-pushed
the
feat/tool-permission-guard
branch
from
July 22, 2026 15:48
3151607 to
848ef89
Compare
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
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.
What
Add a standalone, host-agnostic permission engine for agent tool calls:
guard/— decides allow/ask/deny for a tool call from a set of policy rules. No dependency on OpenAgent (no object/model/beego), so it can be reused as-is by other agents.shellcmd/— extracts the executables a shell command line would run, so a permission layer can allow/deny by program name (git, rm, sudo, …) instead of fragile substring matching.Both packages ship with unit tests and are not yet wired into the tool-call path — that lands in follow-up PRs for issue #2462.
Ref: #2462