Skip to content

fix: soften intercom response enforcement to prevent chat loops - #23

Merged
elecnix merged 1 commit into
mainfrom
fix/soften-intercom-must-respond
Jul 10, 2026
Merged

fix: soften intercom response enforcement to prevent chat loops#23
elecnix merged 1 commit into
mainfrom
fix/soften-intercom-must-respond

Conversation

@elecnix

@elecnix elecnix commented Jul 10, 2026

Copy link
Copy Markdown
Owner

Rule #7 and the per-message context directive both used forceful MUST/DO NOT language that compelled agents to always respond to every intercom message. Combined with inboundTrigger=always, this created infinite reply loops where agents exchanged pleasantries endlessly.

Changes

Rule #7 (system prompt): Replace "MUST respond" with conditional — agents should only reply when there's substance to contribute (questions, decisions, findings, help). Never reply just to acknowledge receipt, say thanks, or "close the loop." Ask messages still require prompt replies since the sender is blocked.

Per-message directive (context event handler): Replace the forceful "⚠️ DO NOT reply in normal chat. You MUST respond using the intercom tool" with a gentle reminder to respond only if meaningful, otherwise continue working.

Behavior

Scenario Before After
send("task done") MUST reply → triggers turn → MUST reply → infinite loop Agent continues working, no reply
ask("which API?") MUST reply promptly Replies promptly (same — asker is blocked)
send("found a bug") MUST reply "thanks/looking" → loop Agent just fixes the bug

— scarlet-tahr-17

Rule #7 and the per-message directive both used MUST/DO NOT language
that compelled agents to always respond to intercom messages. Combined
with inboundTrigger=always, this created infinite reply loops where
agents exchanged pleasantries indefinitely.

Changes:
- Rule #7: replace MUST with conditional — only reply when there's
  substance to contribute; never just to acknowledge receipt
- Directive: replace forceful DO NOT with gentle reminder — respond
  only if meaningful, otherwise continue working
- Ask messages still require prompt replies since the sender is blocked

Co-authored-by: scarlet-tahr-17 <scarlet-tahr-17@pi-agent.local>
@elecnix
elecnix merged commit 0e0aef7 into main Jul 10, 2026
1 check passed
@elecnix
elecnix deleted the fix/soften-intercom-must-respond branch July 10, 2026 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant