feat: per-agent spill controls - #9
Merged
mpfaffenberger merged 1 commit intoAug 17, 2026
Merged
Conversation
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
An individual agent can now disable spill — or add exact-name tool skips — without touching global settings, via its
tools_config:{ "tools_config": { "spill": { "enabled": false, "skip_tools": ["custom_report"] } } }falsedisables; malformed or missing settings keep global behavior (fail open)skip_toolsis additive to the globalspill_skip_toolsset — agents can add exemptions, never remove global onescode_puppy.agent_execution_context(feat: expose per-agent execution context code_puppy#774); on runtimes without it, the import is guarded and global behavior is unchangedTests
Per-agent tests are skipped when the runtime lacks the execution-context module and enabled otherwise:
17 passed, 4 skipped5d63220d):21 passedNo CI pin changes needed — core's CI installs the app from
main, so the tests un-skip automatically once #774 merges. No production changes outside the spill plugin.