Skip to content

fix(telegram): suppress verbose-off tool trace bubbles#760

Merged
artemgetmann merged 1 commit into
mainfrom
codex/telegram-tool-trace-spam-20260518
May 18, 2026
Merged

fix(telegram): suppress verbose-off tool trace bubbles#760
artemgetmann merged 1 commit into
mainfrom
codex/telegram-tool-trace-spam-20260518

Conversation

@artemgetmann
Copy link
Copy Markdown
Owner

Review Fast Path

  • User path fixed: Telegram/Jarvis verbose-off chats no longer show internal 🔧 read, 🔧 memory_search, 🔧 process, or 🔧 exec tool/status trace bubbles while commands run.
  • Proof: focused unit suite passed, full build passed, isolated tester runtime owned this worktree, and live tester bot showed before/after: pre-fix 49758 leaked 🔧 read; post-fix prompt 49764 produced only TOOL_TRACE_SPAM_CHECK_DONE_2 with no 🔧 bubbles.
  • Shared-state footgun removed: tester proof used isolated runtime runtime_worktree=/Users/user/Programming_Projects/openclaw/.worktrees/telegram-tool-trace-spam-20260518, bot @Artem_jarvis_exec_bot, token claim count 1; main Jarvis bot was not touched during validation.
  • Still hurts: this does not redesign progress/final splitting from PR fix(telegram): split progress from final replies #732; it only closes the verbose-off internal tool-label leak.

Why This Matters

Normal Jarvis chats should not expose implementation/tool internals. PR #748 only blocked some exec/cron paths, so other tool labels like read, memory_search, and process could still become Telegram-visible text.

Scope Boundary

  • Suppresses wrench-prefixed internal tool trace text in Telegram when verbose is off.
  • Preserves verbose-on tool traces.
  • Preserves media-bearing tool payload delivery by stripping only the trace caption.
  • Does not suppress the watchdog “Still working...” ping.
  • Does not change main runtime ownership or shared LaunchAgent behavior.

Verification

  • pnpm exec vitest run extensions/telegram/src/bot-message-dispatch.test.ts --pool=forks --maxWorkers=1 passed: 1 file / 76 tests.
  • pnpm build passed.
  • git diff --check passed.
  • Isolated live proof:
    • runtime_ownership=ok
    • runtime_pid=23040
    • runtime_port=24104
    • current_lane_bot=@Artem_jarvis_exec_bot
    • baseline smoke passed before feature test
    • pre-final fix live failure: message 49758 contained 🔧 read\n\nTOOL_TRACE_SPAM_CHECK_DONE
    • post-final fix live pass: messages after prompt 49764 contained only TOOL_TRACE_SPAM_CHECK_DONE_2, no visible 🔧 bubbles

AI Assistance

  • AI-assisted
  • Testing degree: targeted + isolated live-tested

- what changed: suppress all wrench-prefixed Telegram tool trace text when verbose is off while preserving verbose-on traces and media payload delivery

- why: normal Jarvis chats were still exposing internal read/memory/process/tool progress labels after the prior exec/cron-only fix

- risk: scoped to Telegram tool-progress projection; watchdog status pings and normal assistant progress/finals remain visible
@artemgetmann artemgetmann merged commit 331b338 into main May 18, 2026
4 of 9 checks passed
@artemgetmann artemgetmann deleted the codex/telegram-tool-trace-spam-20260518 branch May 18, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant