fix(compaction): respect previous message agent on context injection #10
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
agent: "general"ininjectCompactionContextto respect the actual agent from previous messagesProblem
When compaction context is injected via
injectHookMessage, the agent is hardcoded as"general":This causes the compaction context message to be attributed to "general" agent instead of the actual agent (e.g., "Sisyphus", "oracle") that was active when compaction was triggered.
Solution
Remove the hardcoded
agent: "general"and letinjectHookMessage's existing fallback logic handle it:By not passing an explicit agent,
injectHookMessagewill:originalMessage.agent(undefined)findNearestMessageWithFieldsto get the actual agent from stored messagesThis is a 1-line fix that leverages existing fallback logic.
Testing
bun run build)