-
Notifications
You must be signed in to change notification settings - Fork 1
Labels
agent:copilotAssigned to GitHub Copilot agentAssigned to GitHub Copilot agentpriority:highHigh priorityHigh prioritytier:awaiting-reviewAwaiting senior reviewAwaiting senior review
Description
Summary
The Go kernel binary (dist/go-bin/agentguard-go evaluate) only accepts flattened JSON rules on stdin. It does not resolve:
pack: essentials(or any pack)- YAML policy files
extends:chains
This means calling the Go kernel directly with a standard agentguard.yaml returns "No matching policy rule — default deny (fail-closed)" for all actions, including wildcard allows.
Repro
echo '{"action":"file.write","target":"foo.ts"}' | agentguard-go evaluate --policy agentguard.yaml
# Returns: {"allowed":false,"decision":"deny","reason":"No matching policy rule — default deny (fail-closed)"}Expected
The Go kernel should either:
- Resolve packs/YAML internally (preferred for standalone usage)
- Or document that callers must pre-resolve via
agentguard normalizeand pipe JSON
Context
Found during dogfooding v2.7.3 on bench-devs-platform. Related to #955 (Go kernel not wired into hooks).
Impact
Anyone calling the Go binary directly (CI scripts, custom integrations) will get false deny-all behavior.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
agent:copilotAssigned to GitHub Copilot agentAssigned to GitHub Copilot agentpriority:highHigh priorityHigh prioritytier:awaiting-reviewAwaiting senior reviewAwaiting senior review