Unclear It is not stated what the extra step does to messages that are not marked as verified Slack human turns.
What
Compaction is when Claude Code shortens a long conversation by summarising older parts so it fits in the model's memory. This release adds a way to keep certain rows of a remote session present after that happens:
- The remote input/output layer gets a
repeatAfterCompactionsetter. - When a compaction event is queued with no
session_agent_id, the client appends extra rows fromrowsRepeatedAfterCompactionin the same batch, each with a fresh uuid. Before, only the original events were sent. - Separately, the bridge's handler for incoming messages now calls a function for messages that are not slash commands and lack
verifiedSlackHumanTurn.
Why
Rows that a compaction would otherwise drop can stay in the stored session. These are internals of remote sessions, and what the Slack-turn handling does in practice is not described.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not stated what the extra step does to messages that are not marked as verified Slack human turns.