feat(telegram): add progress assistant preview lane by Fuma2013 · Pull Request #82303 · openclaw/openclaw

Fuma2013 · 2026-05-15T20:23:24Z

Summary

add streaming.progress.assistantPreview to enable assistant partial previews while staying in mode: "progress"
keep the existing Telegram progress/tool/status draft on the answer lane and stream assistant partial text on a separate transient assistant lane
clear/reset the assistant preview lane on final answer delivery and new assistant-message boundaries
regenerate bundled channel config metadata

Real behavior proof

Behavior or issue addressed: Telegram mode: "progress" already shows the useful live tool/status/progress draft, but it drops assistant/Nexus-style answer partials. Switching to block/partial is not acceptable because it replaces the existing progress-live behavior. This patch adds an opt-in second assistant preview lane for answer partials while leaving progress mode intact.
Real environment tested: Mac mini production OpenClaw setup, Telegram enabled/OK, current installed Gateway left untouched at 2026.5.7. Worktree tested at /Users/thomas/.openclaw/workspace/projects/openclaw-upstream/openclaw-telegram-dual-live on branch feat/telegram-progress-assistant-lane.
Exact steps or command run after this patch:

$ openclaw status --deep | sed -n '1,80p'
OpenClaw status
...
Gateway              local · ws://127.0.0.1:18789 ... reachable 56ms ... app 2026.5.7
...
Channels
│ Telegram │ ON      │ OK     │ token config+tokenFile ... accounts 2/2 │

$ node --import tsx - <<'NODE'
import { resolveChannelPreviewStreamMode, resolveChannelProgressDraftAssistantPreview } from './src/plugin-sdk/channel-streaming.ts';
const currentProductionStreaming = { streaming: { mode: 'progress' } };
const afterPatchStreaming = { streaming: { mode: 'progress', progress: { assistantPreview: true } } };
console.log('environment=Mac mini OpenClaw worktree');
console.log('current.mode=' + resolveChannelPreviewStreamMode(currentProductionStreaming));
console.log('current.assistantPreview=' + resolveChannelProgressDraftAssistantPreview(currentProductionStreaming));
console.log('after.mode=' + resolveChannelPreviewStreamMode(afterPatchStreaming));
console.log('after.assistantPreview=' + resolveChannelProgressDraftAssistantPreview(afterPatchStreaming));
NODE

Evidence after fix: terminal capture from the patched OpenClaw worktree:

environment=Mac mini OpenClaw worktree
current.mode=progress
current.assistantPreview=false
after.mode=progress
after.assistantPreview=true

Supplemental local verification:

$ npx pnpm config:channels:check
$ npx pnpm vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts extensions/telegram/src/bot.helpers.test.ts
Test Files  4 passed (4)
Tests       88 passed (88)

$ npx pnpm check:changed
Process exited with code 0.

Observed result after fix: The patched config resolver keeps the existing production-style progress mode unchanged by default (assistantPreview=false) and enables the new additive assistant preview only when streaming.progress.assistantPreview=true. The Telegram dispatch test covers the actual lane split: progress/tool updates remain on the progress draft and assistant partials update the separate assistant lane.
What was not tested: Production activation against the installed Gateway, real Telegram message delivery from the patched branch, and Gateway restart were intentionally skipped. This PR is meant to be merged/released first; local production activation should happen later via config after release.

Testing

npx pnpm config:channels:check
npx pnpm vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts extensions/telegram/src/bot.helpers.test.ts
npx pnpm check:changed

Notes

Existing off, partial, block, and progress semantics stay unchanged by default.
The new behavior is opt-in via streaming.progress.assistantPreview: true.

clawsweeper · 2026-05-15T20:32:33Z

Codex review: needs real behavior proof before merge. Reviewed June 20, 2026, 6:11 PM ET / 22:11 UTC.

Summary
This PR adds a Telegram-only streaming.progress.assistantPreview option, routes progress-mode assistant partials through a separate transient draft lane, updates cleanup/docs/config metadata, and adds focused regression tests.

PR surface: Source +56, Tests +62, Docs +18, Generated 0. Total +136 across 12 files.

Reproducibility: not applicable. this is a feature PR rather than a bug report. Current-main source confirms the baseline behavior that Telegram progress mode drops answer-lane partials.

Review metrics: 1 noteworthy metric.

Telegram Config Surface: 1 added. The new streaming.progress.assistantPreview key needs explicit default, schema, docs, metadata, and upgrade/product review before merge.

Stored data model
Persistent data-model change detected: unknown-data-model-change: src/config/bundled-channel-config-metadata.generated.ts. Confirm migration or upgrade compatibility proof before merge.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🧂 unranked krab
Patch quality: 🐚 platinum hermit
Result: blocked until stronger real behavior proof is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

Refresh the branch so GitHub can produce a clean merge result.
[P1] Add redacted Telegram Desktop, bot-to-bot live output, or logs proving the enabled progress draft plus assistant preview lane updates, clears, and final delivery ordering.
Update the PR body with the proof so ClawSweeper can re-review automatically; if that does not happen, ask a maintainer for @clawsweeper re-review.

Proof guidance:

[P1] Needs stronger real behavior proof before merge: The PR supplies terminal resolver output, tests, and CI, but not redacted real Telegram proof of the enabled two-lane behavior; screenshots, recordings, terminal/live output, linked artifacts, or redacted logs should show the changed flow and avoid private IPs, keys, phone numbers, non-public endpoints, and other private details before the PR body is updated for re-review. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Mantis proof suggestion
Native Telegram proof would directly show whether the second assistant preview lane updates and clears without disrupting the progress draft or final answer. A maintainer can ask Mantis to capture proof by posting this exact PR comment:

@openclaw-mantis telegram desktop proof: with streaming.progress.assistantPreview=true, show the progress draft and separate assistant preview updating, then the preview clearing before final answer delivery.

Risk before merge

[P1] GitHub currently reports the PR head as dirty, so the reviewed head is not a clean merge result against current main.
[P1] The PR changes visible Telegram streaming and draft cleanup ordering, but the supplied proof is resolver output, tests, and CI rather than redacted Telegram Desktop, bot-to-bot live output, or runtime logs of the enabled two-lane flow.
[P1] The PR adds a new Telegram config key, so maintainers still need to accept the product direction even though it is Telegram-scoped and default-off.

Maintainer options:

Refresh And Prove Telegram Delivery (recommended)
Rebase or otherwise refresh the branch, then require redacted Telegram Desktop, bot-to-bot live output, or logs showing the enabled progress draft plus assistant preview update, clear, and final delivery order.
Accept Source-Only Transport Risk
Maintainers can intentionally proceed after a clean merge result with source review and CI only, but would own any real Telegram ordering or stale-preview issue found after release.
Pause Until Product Direction Is Confirmed
If maintainers do not want another Telegram streaming config knob, pause or close this PR and route the broader draft-materialization policy through the related issue discussion.

Next step before merge

[P1] Human review is needed because the remaining blockers are branch refresh, product acceptance of the new Telegram config surface, and contributor-supplied real Telegram proof rather than a narrow mechanical repair.

Security
Cleared: The diff does not change workflows, dependencies, lockfiles, credentials, package resolution, downloaded code, or other concrete supply-chain/security surfaces.

Review details

Best possible solution:

Refresh the branch, keep the Telegram-only default-off shape only if maintainers accept the config surface, and merge after real Telegram proof shows the progress draft, assistant preview updates, preview cleanup, and final answer ordering.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a feature PR rather than a bug report. Current-main source confirms the baseline behavior that Telegram progress mode drops answer-lane partials.

Is this the best way to solve the issue?

Yes on the proposed implementation shape, but not merge-ready. The patch is Telegram-scoped and default-off, while the clean merge result, real Telegram behavior, and product acceptance remain unresolved.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against f18ff7551edc.

Label changes

Label justifications:

P2: This is a bounded Telegram streaming improvement with message-delivery implications but no evidence of an urgent production regression.
merge-risk: 🚨 message-delivery: The diff adds a second transient Telegram draft lane whose real transport ordering, cleanup, and final delivery behavior are not proven by tests alone.
rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: The PR supplies terminal resolver output, tests, and CI, but not redacted real Telegram proof of the enabled two-lane behavior; screenshots, recordings, terminal/live output, linked artifacts, or redacted logs should show the changed flow and avoid private IPs, keys, phone numbers, non-public endpoints, and other private details before the PR body is updated for re-review. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram chat streaming behavior that should be easy to demonstrate with a short Telegram Desktop or bot-to-bot proof.

Evidence reviewed

PR surface:

Source +56, Tests +62, Docs +18, Generated 0. Total +136 across 12 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	6	62	6	+56
Tests	4	68	6	+62
Docs	1	18	0	+18
Config	0	0	0	0
Generated	1	5	5	0
Other	0	0	0	0
Total	12	153	17	+136

What I checked:

Current main baseline: Current main still returns before updating answer-lane partials when Telegram streamMode is progress, so the PR's central behavior is not already implemented. (extensions/telegram/src/bot-message-dispatch.ts:1377, f18ff7551edc)
PR assistant lane implementation: PR head creates an assistant draft lane only when progress mode and resolveChannelProgressDraftAssistantPreview are enabled. (extensions/telegram/src/bot-message-dispatch.ts:1003, 48c33c378852)
PR routing and cleanup: PR head redirects answer segments to the assistant lane in progress mode and clears/resets that lane before final answer delivery. (extensions/telegram/src/bot-message-dispatch.ts:1372, 48c33c378852)
New config surface: PR head adds assistantPreview to a Telegram-specific progress schema rather than the shared channel progress schema. (src/config/zod-schema.providers-core.ts:104, 48c33c378852)
Telegram proof policy: The Telegram maintainer note requires real Telegram proof for streaming behavior changes, and this PR changes visible Telegram streaming behavior. (.agents/maintainer-notes/telegram.md:37, f18ff7551edc)
Live mergeability: GitHub live API reports mergeable=false and mergeable_state=dirty for PR head 48c33c378852f634c4c5b6131fad089a4b08d626. (48c33c378852)

Likely related people:

Ayaan Zaidi: Authored the merged Telegram progress/commentary commits from the adjacent interleaved progress lane that touched dispatch, config, docs, and metadata surfaces this PR extends. (role: recent Telegram progress feature contributor; confidence: high; commits: 799a0af74fdd, 41ee6b1dd68c; files: extensions/telegram/src/bot-message-dispatch.ts, src/config/zod-schema.providers-core.ts, docs/channels/telegram.md)
obviyus: Merged adjacent Telegram progress-lane work and also requested native Telegram proof for this PR's visible streaming behavior. (role: recent reviewer and merger; confidence: high; commits: 41ee6b1dd68c, 310d28f719b8; files: extensions/telegram/src/bot-message-dispatch.ts, docs/channels/telegram.md)
Vincent Koc: Current-main history and blame around Telegram dispatch and shared streaming/config regions include recent broad updates by this author. (role: recent area contributor; confidence: medium; commits: 844f405ac1be; files: extensions/telegram/src/bot-message-dispatch.ts, src/channels/streaming.ts, src/config/zod-schema.providers-core.ts)
Peter Steinberger: Older Telegram dispatch and draft-stream test/refactor history makes this a useful fallback routing signal for preview-lane policy questions. (role: adjacent draft-stream and test contributor; confidence: medium; commits: b3b5945bdc93, 3e80bd33e419; files: extensions/telegram/src/bot-message-dispatch.test.ts, extensions/telegram/src/draft-stream.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

obviyus · 2026-05-16T10:05:36Z

@openclaw-mantis verify this PR on Telegram Desktop.

Please generate before/after GIF evidence for the Telegram progress assistant preview lane. Use a slow reply that includes visible tool/status/progress updates and assistant answer partials. The proof should make main show only the existing progress/status lane while assistant partial text is absent, and this PR should show the new separate assistant preview lane updating while the progress lane remains visible.

Fuma2013 · 2026-05-16T17:15:02Z

Update after review/CI refresh:

Rebasing onto current origin/main resolved the DIRTY/conflicting PR state. GitHub now reports mergeable=MERGEABLE, mergeStateStatus=UNSTABLE while CI is running.
Addressed the ClawSweeper finding [P2] Reset the assistant draft stream after clearing it: after clearing the assistant preview lane, the stream now calls forceNewMessage() before resetting lane state, so the next assistant preview cannot reuse a stopped/cleared draft control.
Added regression coverage in bot-message-dispatch.test.ts for the dual-lane progress mode: progress draft remains separate from assistant preview, final answer is sent normally, and assistant preview clear is followed by forceNewMessage().

Local verification on the rebased branch:

npx -y [email protected] exec vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts extensions/telegram/src/bot.helpers.test.ts → 108 passed
npx -y [email protected] config:channels:check → pass
npx -y [email protected] check:changed → pass

Fuma2013 · 2026-06-07T18:46:48Z

Update after rebase onto current origin/main:

Rebased and force-pushed the PR branch; GitHub now reports mergeable=MERGEABLE.
Resolved the streaming helper move by keeping src/plugin-sdk/channel-streaming.ts as the compatibility wrapper and moving the new helper to src/channels/streaming.ts.
Regenerated bundled channel config metadata after the rebase.

Local verification on commit 54b6236c8a981703fab97868207812324af22027:

corepack pnpm check:no-conflict-markers -> pass
corepack pnpm config:channels:check && corepack pnpm config:schema:check -> pass
corepack pnpm exec vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts -> 174 passed

GitHub proof/checks after push:

Real behavior proof -> pass: https://github.com/openclaw/openclaw/actions/runs/27101470959/job/79982840118
preflight -> pass
no-tabs -> pass
dependency-guard / dependency-guard-detect -> pass
broader CI and CodeQL are still running.

@clawsweeper re-review

clawsweeper · 2026-06-07T18:46:50Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27101508828
Updated: 2026-06-07T18:56:29.620Z

Fuma2013 · 2026-06-07T20:28:37Z

Update after addressing the latest ClawSweeper review:

Added Telegram docs coverage for streaming.progress.assistantPreview, including the opt-in progress-mode example and final cleanup behavior.
Added the Telegram config UI hint for streaming.progress.assistantPreview and updated the parent streaming hint.
Regenerated src/config/bundled-channel-config-metadata.generated.ts so the public config metadata stays aligned.
Fixed the check-test-types failure by adding the missing activeChunkIndex field to the DraftLaneState test fixture.

Local verification on commit a3504600bc789cee0a9cc75238187af40d51f481:

corepack pnpm config:channels:check -> pass
corepack pnpm config:schema:check -> pass
corepack pnpm check:test-types -> pass
corepack pnpm exec vitest run extensions/telegram/src/lane-delivery.test.ts -> 35 passed
git diff --check -> pass

GitHub status after push:

check-test-types is no longer failing.
check-docs, check-lint, check-prod-types, Real behavior proof, preflight, security-fast, OpenGrep, and the visible security/quality checks observed so far are passing.
One CI shard was still in progress when this update was posted: checks-node-agentic-control-plane-startup-core.

Known remaining proof gap:

This update addresses the docs/config-help finding. It does not add the requested redacted Telegram Desktop/live-output proof for the enabled two-lane flow; that remains the visible-behavior proof gate called out by ClawSweeper.

@clawsweeper re-review

clawsweeper · 2026-06-07T20:28:40Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27103922070
Updated: 2026-06-07T20:38:01.242Z

Fuma2013 · 2026-06-15T03:14:52Z

Update after rebase onto current origin/main:

Rebased and force-pushed the PR branch to 1692fc3b9b668e34858d6ed38e1b6d6fb0491588.
GitHub now reports mergeable=MERGEABLE; mergeStateStatus=UNSTABLE only because the fresh CI matrix is still running.
Resolved current-main conflicts by moving the assistant-preview resolver into the current src/channels/streaming.ts helper surface, leaving src/plugin-sdk/channel-streaming.ts as the compatibility re-export, and regenerating bundled channel config metadata.
Kept the current progress-draft formatting behavior (label\n\ntool line) in the assistant-preview regression test.

Local verification:

corepack pnpm check:no-conflict-markers -> pass
corepack pnpm config:channels:check && corepack pnpm config:schema:check -> pass
corepack pnpm exec vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts -> 190 passed

Local note:

corepack pnpm check:changed could not complete locally because the delegated Blacksmith Testbox path failed its local crabbox binary sanity check; GitHub CI is running the broad matrix after the push.

Early GitHub checks after push:

Real behavior proof -> pass
preflight -> pass
security-fast -> pass
no-tabs -> pass
dependency-guard / dependency-guard-detect -> pass

@clawsweeper re-review

clawsweeper · 2026-06-15T03:14:55Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27521848623
Updated: 2026-06-15T03:22:34.704Z

Fuma2013 · 2026-06-15T14:55:13Z

@openclaw-mantis telegram desktop proof: with streaming.progress.assistantPreview=true, show the progress draft and separate assistant preview updating, then the preview clearing before final answer delivery. Please capture redacted visible Telegram Desktop or equivalent bot-to-bot live output proof for PR head 48c33c3.

Fuma2013 · 2026-06-15T14:55:31Z

Update after addressing latest blockers:

Rebased PR branch onto current origin/main (c1219d161d).
Fixed check-test-types by restoring activeChunkIndex: 0 on the new assistant lane fixture.
Scoped streaming.progress.assistantPreview to Telegram schema/types instead of shared channel progress config.
Added Telegram config UI hint and Telegram docs/example for the assistant preview lane.
Regenerated bundled channel config metadata.
Adjusted the assistant-preview regression test to current progress updatePreview behavior after rebase.

Local verification on 48c33c3788:

npx -y [email protected] check:test-types -> pass
npx -y [email protected] config:channels:check && npx -y [email protected] config:schema:check -> pass
npx -y [email protected] exec vitest run src/plugin-sdk/channel-streaming.test.ts extensions/telegram/src/bot-message-dispatch.test.ts extensions/telegram/src/lane-delivery.test.ts -> 193 passed
git diff --check -> pass

Visible proof follow-up:

Requested Mantis Telegram Desktop proof in feat(telegram): add progress assistant preview lane #82303 (comment) for the enabled two-lane flow.

@clawsweeper re-review

clawsweeper · 2026-06-15T14:55:34Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

State: Complete
Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
Run: https://github.com/openclaw/clawsweeper/actions/runs/27555575506
Updated: 2026-06-15T15:15:13.933Z

obviyus · 2026-06-21T14:31:19Z

Thanks for the implementation and tests.

We are going to close this because the intended UX is already covered by the existing Telegram streaming modes: progress mode keeps the status/tool draft visible, streaming.progress.commentary can show preamble/commentary text in that progress draft, and partial / block modes are the supported paths for streaming assistant answer text. A separate temporary assistant-preview lane would add a second transient Telegram message plus cleanup/config complexity without a clear product need beyond those existing modes.

Appreciate the contribution.

clawsweeper Bot added the mantis: telegram-visible-proof Mantis should capture Telegram visible proof. label May 15, 2026

This comment was marked as spam.

Sign in to view

Fuma2013 force-pushed the feat/telegram-progress-assistant-lane branch from 6e5a817 to 3ddc9d4 Compare May 16, 2026 17:13

clawsweeper Bot removed the mantis: telegram-visible-proof Mantis should capture Telegram visible proof. label May 16, 2026

Fuma2013 force-pushed the feat/telegram-progress-assistant-lane branch from 3ddc9d4 to ff8fd8b Compare May 17, 2026 21:39

clawsweeper Bot added mantis: telegram-visible-proof Mantis should capture Telegram visible proof. P2 Normal backlog priority with limited blast radius. impact:message-loss Channel message delivery can be lost, duplicated, or misrouted. labels May 17, 2026

clawsweeper Bot temporarily deployed to qa-live-shared May 17, 2026 21:47 Inactive

openclaw deleted a comment from openclaw-mantis Bot May 18, 2026

masatohoshino mentioned this pull request May 26, 2026

feat(agents): show progress while web_fetch is waiting #86950

Closed

clawsweeper Bot mentioned this pull request May 28, 2026

feat(telegram): opt-in interleaved progress lane #87072

Merged

2 tasks

Fuma2013 force-pushed the feat/telegram-progress-assistant-lane branch from ff8fd8b to 54b6236 Compare June 7, 2026 18:45

openclaw-barnacle Bot added the docs Improvements or additions to documentation label Jun 7, 2026

Fuma2013 force-pushed the feat/telegram-progress-assistant-lane branch from a350460 to 1692fc3 Compare June 15, 2026 03:13

openclaw-barnacle Bot removed the docs Improvements or additions to documentation label Jun 15, 2026

clawsweeper Bot added rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. and removed rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. labels Jun 15, 2026

Fuma2013 added 2 commits June 15, 2026 16:49

feat(telegram): add progress assistant preview lane

30c7bdd

fix(telegram): scope assistant preview config

48c33c3

Fuma2013 force-pushed the feat/telegram-progress-assistant-lane branch from 1692fc3 to 48c33c3 Compare June 15, 2026 14:54

openclaw-barnacle Bot added the docs Improvements or additions to documentation label Jun 15, 2026

clawsweeper Bot mentioned this pull request Jun 21, 2026

fix(telegram): materialize streaming progress placeholders #95183

Merged

snowzlmbot mentioned this pull request Jun 21, 2026

feat(telegram): unify progress fallback with assistant preview lane #95522

Closed

obviyus closed this Jun 21, 2026

Uh oh!

Uh oh!

Conversation

Fuma2013 commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Real behavior proof

Testing

Notes

Uh oh!

clawsweeper Bot commented May 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as spam.

obviyus commented May 16, 2026

Uh oh!

Fuma2013 commented May 16, 2026

Uh oh!

Fuma2013 commented Jun 7, 2026

Uh oh!

clawsweeper Bot commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Fuma2013 commented Jun 7, 2026

Uh oh!

clawsweeper Bot commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Fuma2013 commented Jun 15, 2026

Uh oh!

clawsweeper Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Fuma2013 commented Jun 15, 2026

Uh oh!

Fuma2013 commented Jun 15, 2026

Uh oh!

clawsweeper Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

obviyus commented Jun 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Fuma2013 commented May 15, 2026 •

edited

Loading

clawsweeper Bot commented May 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 7, 2026 •

edited

Loading

clawsweeper Bot commented Jun 7, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading

clawsweeper Bot commented Jun 15, 2026 •

edited

Loading