telegram: lower MaxMessageLength to 4000 for HTML expansion margin

The Manager splits at MaxMessageLength before calling Send(), and
Telegram's Send() was re-splitting at 4000 internally. Aligning the
channel-level limit to 4000 avoids that redundant second split while
preserving the safety margin for markdown-to-HTML expansion.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
I Putu Eddy Irawan 2026-03-04 20:46:43 +07:00
parent fe97387f0f
commit 8bd1935efb
2 changed files with 2 additions and 2 deletions

View file

@ -86,7 +86,7 @@ func NewTelegramChannel(cfg *config.Config, bus *bus.MessageBus) (*TelegramChann
telegramCfg, telegramCfg,
bus, bus,
telegramCfg.AllowFrom, telegramCfg.AllowFrom,
channels.WithMaxMessageLength(4096), channels.WithMaxMessageLength(4000),
channels.WithGroupTrigger(telegramCfg.GroupTrigger), channels.WithGroupTrigger(telegramCfg.GroupTrigger),
channels.WithReasoningChannelID(telegramCfg.ReasoningChannelID), channels.WithReasoningChannelID(telegramCfg.ReasoningChannelID),
) )

View file

@ -69,7 +69,7 @@ func newTestChannel(t *testing.T, caller *stubCaller) *TelegramChannel {
require.NoError(t, err) require.NoError(t, err)
base := channels.NewBaseChannel("telegram", nil, nil, nil, base := channels.NewBaseChannel("telegram", nil, nil, nil,
channels.WithMaxMessageLength(4096), channels.WithMaxMessageLength(4000),
) )
base.SetRunning(true) base.SetRunning(true)