The tool-activity block is unbounded within a turn, so a tool-heavy turn can still crowd the answer out of a single Telegram frame.\n\nlive.toolLines (internal/channels/telegram/live.go) accumulates one rendered line per tool call with no cap, unlike answerBuf. Measured: 14 calls rendered ~1043 runes, roughly 27% of liveBodyMaxRunes (3900). The frame clamp then bites and the answer is what gets summarised away.\n\nSplit out of GitHub #837 (fixed by PR #838).\n\nDirection: cap the tool block (count or total runes) so the answer keeps the majority of the frame; prefer the most recent activity with a '+N earlier' indicator. Reference: duckbugio/flock core/chat/progress.go activity ring + frame budget.
Imported from beads archie-core-4sor · GitHub #839 · type bug · priority P2 · created 2026-09-17 · closed 2026-09-17
The tool-activity block is unbounded within a turn, so a tool-heavy turn can still crowd the answer out of a single Telegram frame.\n\nlive.toolLines (internal/channels/telegram/live.go) accumulates one rendered line per tool call with no cap, unlike answerBuf. Measured: 14 calls rendered ~1043 runes, roughly 27% of liveBodyMaxRunes (3900). The frame clamp then bites and the answer is what gets summarised away.\n\nSplit out of GitHub #837 (fixed by PR #838).\n\nDirection: cap the tool block (count or total runes) so the answer keeps the majority of the frame; prefer the most recent activity with a '+N earlier' indicator. Reference: duckbugio/flock core/chat/progress.go activity ring + frame budget.
### Close reason
Landed in 8dd8841; GitHub #839 already closed.
---
_Imported from beads `archie-core-4sor` · GitHub #839 · type bug · priority P2 · created 2026-09-17 · closed 2026-09-17_
sam
added the mediumbug labels 2026-10-27 13:38:54 +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.
The tool-activity block is unbounded within a turn, so a tool-heavy turn can still crowd the answer out of a single Telegram frame.\n\nlive.toolLines (internal/channels/telegram/live.go) accumulates one rendered line per tool call with no cap, unlike answerBuf. Measured: 14 calls rendered ~1043 runes, roughly 27% of liveBodyMaxRunes (3900). The frame clamp then bites and the answer is what gets summarised away.\n\nSplit out of GitHub #837 (fixed by PR #838).\n\nDirection: cap the tool block (count or total runes) so the answer keeps the majority of the frame; prefer the most recent activity with a '+N earlier' indicator. Reference: duckbugio/flock core/chat/progress.go activity ring + frame budget.
Close reason
Landed in 8dd8841; GitHub #839 already closed.
Imported from beads
archie-core-4sor· GitHub #839 · type bug · priority P2 · created 2026-09-17 · closed 2026-09-17