AytuncYildizli a44843507f fix(slack): restore persistent per-channel session routing (#32320) ...

Top-level channel messages were creating isolated per-message sessions because roomThreadId fell through to threadContext.messageTs whenever replyToMode was not off.

Introduced in #10686, every new channel message got its own session key (agent:...🧵<messageTs>), breaking conversation continuity.

Fix: only derive thread-specific session keys for actual thread replies. Top-level channel messages stay on the per-channel session key regardless of replyToMode.

Fixes #32285

2026-03-03 01:00:49 +00:00

..

dispatch.streaming.test.ts

refactor(config): unify streaming config across channels

2026-02-21 19:53:42 +01:00

dispatch.ts

refactor: harden plugin install flow and main DM route pinning

2026-03-02 21:22:38 +00:00

prepare-content.ts

refactor: modularize slack/config/cron/daemon internals

2026-03-02 22:30:21 +00:00

prepare-thread-context.ts

refactor: modularize slack/config/cron/daemon internals

2026-03-02 22:30:21 +00:00

prepare.test-helpers.ts

refactor: dedupe channel and gateway surfaces

2026-03-02 19:57:33 +00:00

prepare.test.ts

test(perf): trim slack, hook, and plugin-validation test overhead

2026-03-03 00:43:01 +00:00

prepare.thread-session-key.test.ts

fix(slack): restore persistent per-channel session routing (#32320)

2026-03-03 01:00:49 +00:00

prepare.ts

fix(slack): restore persistent per-channel session routing (#32320)

2026-03-03 01:00:49 +00:00

types.ts

fix(slack): resolve replyToMode per-message using chat type (#24717)

2026-03-01 10:21:01 -06:00