Skip to content

fix(telegram): add safe verbose tool completion summaries#409

Merged
artemgetmann merged 1 commit into
mainfrom
codex/telegram-verbose-lane-20260408
Apr 9, 2026
Merged

fix(telegram): add safe verbose tool completion summaries#409
artemgetmann merged 1 commit into
mainfrom
codex/telegram-verbose-lane-20260408

Conversation

@artemgetmann
Copy link
Copy Markdown
Owner

@artemgetmann artemgetmann commented Apr 8, 2026

Summary

  • add a safe tool-completion summary line for verbose tool sessions (status + non-sensitive output hint)
  • keep full raw tool output gated behind existing verbose=full behavior
  • preserve verbose-off behavior and existing approval-prompt special handling

Why

Native Telegram /verbose on sessions surfaced tool start lines but often looked opaque after execution. This adds a concise completion trace without exposing raw payloads by default.

Before / After (Telegram verbose-on example)

Before:

  • 🔧 Exec: pwd
  • final assistant text only (e.g. /Users/user)

After:

  • 🔧 Exec: pwd
  • ✅ 🔧 Exec: pwd · completed · text output (1 line, 11 chars)
  • final assistant text

Validation

  • pnpm -s vitest src/agents/pi-embedded-subscribe.handlers.tools.test.ts src/auto-reply/reply/dispatch-from-config.test.ts
  • pnpm -s vitest extensions/telegram/src/bot-message-dispatch.test.ts

- what: emit tool completion summary lines (status + output hint) when tool summaries are enabled and full output is off

- why: native Telegram verbose sessions showed tool start lines only, which kept command execution opaque

- risk: verbose-on channels may see one extra tool line per completed tool call; verbose-off remains unchanged
@artemgetmann artemgetmann merged commit d2c840f into main Apr 9, 2026
3 of 10 checks passed
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