惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

U
Unit 42
Google DeepMind News
Google DeepMind News
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
MongoDB | Blog
MongoDB | Blog
I
InfoQ
N
Netflix TechBlog - Medium
T
Tailwind CSS Blog
量子位
博客园 - 叶小钗
月光博客
月光博客
IT之家
IT之家
G
Google Developers Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
小众软件
小众软件
S
SegmentFault 最新的问题
Engineering at Meta
Engineering at Meta
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
aimingoo的专栏
aimingoo的专栏
云风的 BLOG
云风的 BLOG
Vercel News
Vercel News
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
宝玉的分享
宝玉的分享

Recent Commits to openclaw:main

test: merge chat side-result checks · openclaw/openclaw@ddd2c2a test: merge cron history checks · openclaw/openclaw@f7eb746 test: merge responsive navigation shell checks · openclaw/openclaw@c2e4b47 docs(changelog): add codex oauth fixes · openclaw/openclaw@628e6cd test: merge navigation routing cases · openclaw/openclaw@5d8cecb Tests: mock channel registry bundled fallback · openclaw/openclaw@2b08233 Secrets: avoid broad web search discovery for single plugin config · openclaw/openclaw@a464f59 test: merge config view browser checks · openclaw/openclaw@20cf511 fix(status): align oauth health with runtime · openclaw/openclaw@eed7116 feat: add macOS screen snapshots for monitor preview (#67954) thanks … · openclaw/openclaw@f377db1 fix: report shared auth scopes in hello-ok (#67810) thanks @BunsDev · openclaw/openclaw@0b6c39b Auto-reply: avoid eager bundled route fallback · openclaw/openclaw@3ea1bf4 Tests: narrow session binding contract setup · openclaw/openclaw@54e4e16 fix(macOS): enable undo/redo in webchat composer text input (#34962) · openclaw/openclaw@00951dc Tests: speed up channel setup promotion · openclaw/openclaw@82b529a Docs: refresh agent instructions · openclaw/openclaw@5775fe2 fix(auth): serialize OAuth refresh across agents to fix #26322 (#67876) · openclaw/openclaw@8e79080 test: allow ollama public surface boundary test · openclaw/openclaw@7d4f1a6 Docs: add test performance guardrails · openclaw/openclaw@89706d3 Tests: restore context-engine usage proof · openclaw/openclaw@e4c4f95 Tests: slim context engine runtime coverage · openclaw/openclaw@74c198f ci: retry failed custom checkouts · openclaw/openclaw@0ee5baf test: trim duplicate provider auth onboarding cases · openclaw/openclaw@1ffc02e matrix: fix sessions_spawn --thread subagent session spawning (#67643) · openclaw/openclaw@1ce2596 test: reduce auth choice fixture churn · openclaw/openclaw@857b9cd test: mock health status config boundaries · openclaw/openclaw@9d5ab4a test: mock onboard config io boundary · openclaw/openclaw@299694d test: mock legacy state plugin boundaries · openclaw/openclaw@2713089 test: mock channel install boundaries · openclaw/openclaw@b945248 test: mock doctor preview channel boundaries · openclaw/openclaw@b1a3ad4
fix(telegram): separate progress drafts from final replie...
obviyus · 2026-05-06 · via Recent Commits to openclaw:main
Original file line numberDiff line numberDiff line change

@@ -278,7 +278,7 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"

278278

Requirement:

279279
280280

- `channels.telegram.streaming` is `off | partial | block | progress` (default: `partial`)

281-

- `progress` keeps one editable status draft and updates it with tool progress until final delivery

281+

- `progress` keeps one editable status draft for tool progress, clears it at completion, and sends the final answer as a normal message

282282

- `streaming.preview.toolProgress` controls whether tool/progress updates reuse the same edited preview message (default: `true` when preview streaming is active)

283283

- `streaming.preview.commandText` controls command/exec detail inside those tool-progress lines: `raw` (default, preserves released behavior) or `status` (tool label only)

284284

- legacy `channels.telegram.streamMode` and boolean `streaming` values are detected; run `openclaw doctor --fix` to migrate them to `channels.telegram.streaming.mode`

@@ -317,7 +317,7 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"

317317

}

318318

```

319319
320-

For progress-draft mode, put the same command-text policy under `streaming.progress`:

320+

Use `progress` mode when you want visible tool progress without editing the final answer into that same message. Put the command-text policy under `streaming.progress`:

321321
322322

```json

323323

{

@@ -345,6 +345,7 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"

345345
346346

- short DM/group/topic previews: OpenClaw keeps the same preview message and performs the final edit in place

347347

- long text finals that split into multiple Telegram messages reuse the existing preview as the first final chunk when possible, then send only the remaining chunks

348+

- progress-mode finals clear the status draft and use normal final delivery instead of editing the draft into the answer

348349

- if the final edit fails before the completed text is confirmed, OpenClaw uses normal final delivery and cleans up the stale preview

349350
350351

For complex replies (for example media payloads), OpenClaw falls back to normal final delivery and then cleans up the preview message.

Original file line numberDiff line numberDiff line change

@@ -161,6 +161,7 @@ Telegram:

161161
162162

- Uses `sendMessage` + `editMessageText` preview updates across DMs and group/topics.

163163

- Final text edits the active preview in place; long finals reuse that message for the first chunk and send only the remaining chunks.

164+

- `progress` mode keeps tool progress in an editable status draft, clears that draft at completion, and sends the final answer through normal delivery.

164165

- If the final edit fails before the completed text is confirmed, OpenClaw uses normal final delivery and cleans up the stale preview.

165166

- Preview streaming is skipped when Telegram block streaming is explicitly enabled (to avoid double-streaming).

166167

- `/reasoning stream` can write reasoning to a transient preview that is deleted after final delivery.

Original file line numberDiff line numberDiff line change

@@ -919,6 +919,40 @@ describe("dispatchTelegramMessage draft streaming", () => {

919919

expect(deliverReplies).not.toHaveBeenCalled();

920920

});

921921
922+

it("keeps progress updates in a draft and sends the final answer normally", async () => {

923+

const { answerDraftStream } = setupDraftStreams({ answerMessageId: 2001 });

924+

dispatchReplyWithBufferedBlockDispatcher.mockImplementation(

925+

async ({ dispatcherOptions, replyOptions }) => {

926+

await replyOptions?.onToolStart?.({ name: "exec", phase: "start" });

927+

await replyOptions?.onItemEvent?.({

928+

kind: "command",

929+

name: "exec",

930+

progressText: "git rev-parse --abbrev-ref HEAD",

931+

});

932+

await dispatcherOptions.deliver({ text: "Branch is up to date" }, { kind: "final" });

933+

return { queuedFinal: true };

934+

},

935+

);

936+
937+

await dispatchWithContext({

938+

context: createContext(),

939+

streamMode: "progress",

940+

telegramCfg: { streaming: { mode: "progress" } },

941+

});

942+
943+

expect(answerDraftStream.update).toHaveBeenCalledWith(

944+

expect.stringMatching(/`🛠 Exec: git rev-parse --abbrev-ref HEAD`$/),

945+

);

946+

expect(answerDraftStream.update).not.toHaveBeenCalledWith("Branch is up to date");

947+

expect(answerDraftStream.clear).toHaveBeenCalledTimes(1);

948+

expect(deliverReplies).toHaveBeenCalledWith(

949+

expect.objectContaining({

950+

replies: [expect.objectContaining({ text: "Branch is up to date" })],

951+

}),

952+

);

953+

expect(editMessageTelegram).not.toHaveBeenCalled();

954+

});

955+
922956

it("streams the first long final chunk and sends follow-up chunks", async () => {

923957

const { answerDraftStream } = setupDraftStreams({ answerMessageId: 2001 });

924958

const longText = "one ".repeat(80);

Original file line numberDiff line numberDiff line change

@@ -901,6 +901,16 @@ export const dispatchTelegramMessage = async ({

901901

deliveryState.markDelivered();

902902

},

903903

});

904+

const deliverProgressModeFinalAnswer = async (

905+

payload: ReplyPayload,

906+

text: string,

907+

): Promise<LaneDeliveryResult> => {

908+

await answerLane.stream?.clear();

909+

resetDraftLaneState(answerLane);

910+

const delivered = await sendPayload(applyTextToPayload(payload, text), { durable: true });

911+

answerLane.finalized = true;

912+

return delivered ? { kind: "sent" } : { kind: "skipped" };

913+

};

904914
905915

if (isDmTopic) {

906916

try {

@@ -1042,13 +1052,18 @@ export const dispatchTelegramMessage = async ({

10421052

if (segment.lane === "reasoning") {

10431053

reasoningStepState.noteReasoningHint();

10441054

}

1045-

const result = await deliverLaneText({

1046-

laneName: segment.lane,

1047-

text: segment.text,

1048-

payload,

1049-

infoKind: info.kind,

1050-

buttons: telegramButtons,

1051-

});

1055+

const result =

1056+

streamMode === "progress" &&

1057+

segment.lane === "answer" &&

1058+

info.kind === "final"

1059+

? await deliverProgressModeFinalAnswer(payload, segment.text)

1060+

: await deliverLaneText({

1061+

laneName: segment.lane,

1062+

text: segment.text,

1063+

payload,

1064+

infoKind: info.kind,

1065+

buttons: telegramButtons,

1066+

});

10521067

if (info.kind === "final") {

10531068

emitPreviewFinalizedHook(result);

10541069

}