Repository navigation
[FEATURE]: ACP: expose compaction summary marker so chat clients can suppress compaction dumps #40494
Description
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement
Chat clients connected via the ACP protocol (e.g. opencode-chat-bridge, which forwards ACP updates to Matrix/Telegram) cannot distinguish an auto-compaction summary from a normal assistant reply.
OpenCode already marks the summary internally:
- the summary assistant message is created with
summary: trueandmode: "compaction" - the auto-continue follow-up text part has
metadata: { compaction_continue: true } - a
session.compactedevent is published when compaction completes
But packages/opencode/src/acp/event.ts only handles permission.asked, message.part.updated, message.part.delta and forwards plain agent_message_chunk updates with no message-level info. The session.compacted event is never forwarded to ACP clients. As a result, chat users see an unexplained wall of text when the session auto-compacts.
Suggested fix: include message info (summary, mode) in the agent_message_chunk sessionUpdate payload (and in session/load replay), and/or forward the session.compacted event as a dedicated ACP notification.
Activity
nexxeln commentedon Oct 1, 2026
hey! this should be fixed in v2 now 🙏 if you're still on 1.x, upgrading to v2 should sort it out. let us know if you still hit it after upgrading and we'll take another look!
nexxeln commentedon Oct 6, 2026
Fixed on v2. #52485 marks compactions with _meta["opencode/compaction"] on session_info_update, and #52737 sends ACP's compaction_update and compaction_summary_chunk to clients that advertise session.compaction. The summary is never sent as agent_message_chunk, so chat bridges can hide it.