Batch rapid-fire inbound text events from the same sender/channel into a single dispatch instead of invoking the agent loop once per fragment. Chat clients (Telegram in particular) often split a user's thought across several quick messages; dispatching each separately wastes a full agent turn per fragment and can interleave responses oddly.
Context for implementers
No aggregator exists yet in internal/gateway. This sits upstream of the agent-loop dispatch, after platform adapters normalize events into MessageEvent (internal/gateway/messageevent.go) but before a turn is started (see internal/gateway/turn.go, turns.go).
Acceptance Criteria
Text events from the same channel arriving within a short configurable window are coalesced into one aggregated event before dispatch. A single non-batched message is not delayed by more than the window. Aggregation window is configurable, not hardcoded. Covered by a test using an injected clock.
Close reason
Closed
Imported from beads archie-core-1786637492528-105-c2b3caab · GitHub #126 · type task · priority P2 · created 2026-08-08 · closed 2026-10-01
Batch rapid-fire inbound text events from the same sender/channel into a single dispatch instead of invoking the agent loop once per fragment. Chat clients (Telegram in particular) often split a user's thought across several quick messages; dispatching each separately wastes a full agent turn per fragment and can interleave responses oddly.
### Context for implementers
No aggregator exists yet in `internal/gateway`. This sits upstream of the agent-loop dispatch, after platform adapters normalize events into `MessageEvent` (`internal/gateway/messageevent.go`) but before a turn is started (see `internal/gateway/turn.go`, `turns.go`).
### Acceptance Criteria
Text events from the same channel arriving within a short configurable window are coalesced into one aggregated event before dispatch. A single non-batched message is not delayed by more than the window. Aggregation window is configurable, not hardcoded. Covered by a test using an injected clock.
### Close reason
Closed
---
_Imported from beads `archie-core-1786637492528-105-c2b3caab` · GitHub #126 · type task · priority P2 · created 2026-08-08 · closed 2026-10-01_
sam
added the mediumtask labels 2026-10-27 13:37:06 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Batch rapid-fire inbound text events from the same sender/channel into a single dispatch instead of invoking the agent loop once per fragment. Chat clients (Telegram in particular) often split a user's thought across several quick messages; dispatching each separately wastes a full agent turn per fragment and can interleave responses oddly.
Context for implementers
No aggregator exists yet in
internal/gateway. This sits upstream of the agent-loop dispatch, after platform adapters normalize events intoMessageEvent(internal/gateway/messageevent.go) but before a turn is started (seeinternal/gateway/turn.go,turns.go).Acceptance Criteria
Text events from the same channel arriving within a short configurable window are coalesced into one aggregated event before dispatch. A single non-batched message is not delayed by more than the window. Aggregation window is configurable, not hardcoded. Covered by a test using an injected clock.
Close reason
Closed
Imported from beads
archie-core-1786637492528-105-c2b3caab· GitHub #126 · type task · priority P2 · created 2026-08-08 · closed 2026-10-01