feat(ambient): require self-contained context in delegation prompts - #304
Merged
Conversation
Add an operating rule to the orchestrator charter: every subagent delegation must be self-contained — goal, constraints, relevant session decisions and facts, and exact paths. Deliverables that draw on the conversation (issues, PRs, reports) must carry the substance in the prompt rather than a pointer to it. Charter grows from 2177 → 2452 bytes (~600 tokens), well within the 4096-byte runtime limit enforced by session-start-orchestrator. Sync installed runtime copy and update CLAUDE.md token estimate. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
The orchestrator charter tells the orchestrator session what to delegate and to which model tier, but never stated that subagents start with a blank context. This led to observed failures where the orchestrator asked an agent to create a GitHub issue summarizing the conversation without passing the conversation's substance — the issue came out missing key information and needed a second pass to fix.
This PR adds one operating rule to the charter that closes this gap.
Changes
New operating rule in
src/assets/scripts/hooks/assets/orchestrator-charter.md(inserted after the "Decompose mainline" bullet, before "Parallelize"):Mechanical consequences:
session-start-orchestratorCLAUDE.md: updated token estimate from ~535 to ~600CHANGELOG.md: entry added under## [Unreleased]~/.devflow/scripts/hooks/assets/orchestrator-charter.mdsynced;diffconfirms files are identicalBreaking Changes
None.
Reviewer Focus Areas
Test Results