fix(telegram): suppress verbose-off tool trace bubbles#760
Merged
Conversation
- 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review Fast Path
🔧 read,🔧 memory_search,🔧 process, or🔧 exectool/status trace bubbles while commands run.49758leaked🔧 read; post-fix prompt49764produced onlyTOOL_TRACE_SPAM_CHECK_DONE_2with no🔧bubbles.runtime_worktree=/Users/user/Programming_Projects/openclaw/.worktrees/telegram-tool-trace-spam-20260518, bot@Artem_jarvis_exec_bot, token claim count1; main Jarvis bot was not touched during validation.Why This Matters
Normal Jarvis chats should not expose implementation/tool internals. PR #748 only blocked some
exec/cronpaths, so other tool labels likeread,memory_search, andprocesscould still become Telegram-visible text.Scope Boundary
Verification
pnpm exec vitest run extensions/telegram/src/bot-message-dispatch.test.ts --pool=forks --maxWorkers=1passed:1 file / 76 tests.pnpm buildpassed.git diff --checkpassed.runtime_ownership=okruntime_pid=23040runtime_port=24104current_lane_bot=@Artem_jarvis_exec_bot49758contained🔧 read\n\nTOOL_TRACE_SPAM_CHECK_DONE49764contained onlyTOOL_TRACE_SPAM_CHECK_DONE_2, no visible🔧bubblesAI Assistance