feat: inherit embedded AGENTS.md operating rules for sub-agents#1490
Merged
Conversation
92a6e92 to
2b31957
Compare
This was referenced Jun 25, 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
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.
Problem
Sub-agents spawned via
spawn_agentdo not receive the embeddedAGENTS.mdoperating rules layer that main-agent sessions get. They only receive their own markdown body, optional project instructions, and the hardcodedHeadlessExecutionContract.This means sub-agents operate without the core safety guardrails that main agents inherit:
Solution
Sub-agents now inherit the embedded
AGENTS.mdoperating rules alongside their existing context:Changes
ISystemPromptProvider.csGetOperatingRules(TrustAudience)to the interfaceFileSystemPromptProvider(substituted embedded AGENTS.md for Team/Personal, null for Public)nullimplementations toStaticSystemPromptProviderandNullSystemPromptProviderSubAgentProtocol.csOperatingRulesproperty toSubAgentDefinitionrecordSubAgentSpawner.csResolveOperatingRules()that calls_promptProvider.GetOperatingRules(context.Audience)SubAgentDefinitionat spawn timeSubAgentActor.csBuildSystemPrompt()to assemble the full identity stack:SystemPromptAssembler.Assemble(agents: definition.OperatingRules, ...)HeadlessExecutionContractalways appended at the bottomNotes
SOUL.mdandTOOLING.mdare intentionally excluded — sub-agents don't need personal identity or redundant tooling info (tool index already available)nullgracefully