fix(agent): cue driven agents to reply in-channel, not into the session log (RIG-2664) - #583
Open
rigel-mintaka wants to merge 1 commit into
Conversation
…on log (RIG-2664) A delivered channel message was injected as a bare `Topic <id>:\n<text>` digest with no instruction to reply through the channel. A driven agent would answer into its own session transcript — which the operator does not read — so its reply was invisible to whoever asked. This was a top dogfoodability gap: the Manager looked unresponsive when it had in fact 'replied', just nowhere the operator could see. Two changes: (1) formatDeliversForPrompt now appends ONE reply-in-channel cue for the whole coalesced batch, naming the topics and directing the agent to post back with comms_post_message; (2) the manager block-0 (config/prompts/manager/SYSTEM.md) states the load-bearing rule explicitly — the operator reads the channel, not your session log, so every answer must be posted to a channel. Refs RIG-2664 Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Compass engineering docs preview: https://compass-rig-2664-channel-rep.compass-eng-docs.pages.dev Deployed from |
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
1 participant
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.
This PR is part of a stack containing 3 PRs:
mainA delivered channel message was injected as a bare
Topic <id>:\n<text>digest with no instruction to reply through the channel. A driven agent would answer into its own session transcript — which the operator does not read — so its reply was invisible to whoever asked. This was a top dogfoodability gap: the Manager looked unresponsive when it had in fact 'replied', just nowhere the operator could see.Two changes: (1) formatDeliversForPrompt now appends ONE reply-in-channel cue for the whole coalesced batch, naming the topics and directing the agent to post back with comms_post_message; (2) the manager block-0 (config/prompts/manager/SYSTEM.md) states the load-bearing rule explicitly — the operator reads the channel, not your session log, so every answer must be posted to a channel.
Refs RIG-2664
Co-authored-by: Matt Wilkinson matt@rigel.build