Skip to content

fix(telegram): retain work log before final answer#1096

Merged
artemgetmann merged 4 commits into
mainfrom
codex/telegram-work-log-v11-20260706
Jul 8, 2026
Merged

fix(telegram): retain work log before final answer#1096
artemgetmann merged 4 commits into
mainfrom
codex/telegram-work-log-v11-20260706

Conversation

@artemgetmann

@artemgetmann artemgetmann commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • retain completed Telegram progress as a collapsed Work log message before final-answer delivery
  • keep the final answer on a separate durable send after the Work Log is frozen
  • simplify Work Log copy to Work log collapsed and natural entries expanded, with no counts/tool footer
  • preserve meaningful internal newlines inside retained progress entries

Validation

  • pnpm exec vitest run extensions/telegram/src/work-log.test.ts extensions/telegram/src/bot-message-dispatch.test.ts
  • GitHub checks: green on head ec7be0445ecfc5319052687e54b72f0c20bb7bff
  • Live isolated tester-bot proof was run from stacked branch fix(telegram): preserve plan progress history #1105 on commit 88746ac70559671cd14fa7c4b9984fde9a5107cf, which includes this PR. Baseline passed against @Artem_jarvis_email_bot; TTS remained enabled. Transcript proof: prompt 54905, Work Log 54906, final answer 54908, voice 54909.

Proof Gaps

  • openclaw screen record --app Telegram failed with gateway 1006, so no screen recording artifact was produced.
  • Inline Show/Hide was visually present and unit-covered, but not live-clicked because Telegram Desktop did not expose message-level controls through GUI-control and the Telegram-as-me CLI has no callback-click command.

Codex added 2 commits July 7, 2026 13:42
- what: retain Telegram progress previews as a compact Work log with Show/Hide details before final text starts.
- why: prevents final-answer text from briefly appearing inside the progress bubble and removes internal counts/tool labels from consumer UI.
- risk: Telegram live behavior still needs isolated tester-bot proof; covered here with targeted dispatch/progress/callback unit tests.
- what changed: force final answer text through durable send when progress is retained as Work Log
- why: Telegram could finalize a post-progress preview into a blank answer bubble while TTS spoke the real final
- behavior/risk: scoped to Work Log final-boundary routing; normal streamed finals still use preview finalization
@artemgetmann artemgetmann force-pushed the codex/telegram-work-log-v11-20260706 branch from 2f28e7d to a3e3e06 Compare July 7, 2026 05:43
- What: keep meaningful internal newlines inside retained Telegram Work Log entries.

- Why: expanded plan/checklist progress should stay readable instead of collapsing into one line.

- Risk: low; scoped to Work Log normalization and covered by focused tests.
@artemgetmann artemgetmann marked this pull request as ready for review July 7, 2026 06:37
@artemgetmann artemgetmann merged commit 4f809e9 into main Jul 8, 2026
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant