google-gemini/gemini-cli

[Hooks] Debug logs are too verbose

Open

#16,629 建立於 2026年1月14日

在 GitHub 查看
 (5 留言) (0 反應) (1 負責人)TypeScript (103,992 star) (13,657 fork)batch import
area/agenthelp wantedkind/bugpriority/p2priority/p3status/bot-triaged

描述

What happened?

Currently with --debug turned on and hooks enabled, the debug log is spammed with essentially the entire agent trajectory for every hook lifecycle entrypoint. This makes it almost impossible to navigate and understand the debug logs.

What did you expect to happen?

A short debug message of which hook lifecycle point was reached and which detected hooks were invoked

Client information

N/A

Login information

No response

Anything else we need to know?

No response

貢獻者指南

技術棧
typescript
領域
clideveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with hooks systemUnderstanding of debug logs
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Examine the hooks implementation, particularly the debugging/logging statements in the hook lifecycle entrypoints. Locate where the agent trajectory is logged and propose a change to output only the hook point and detected hooks. Since this issue has an assignee, coordinate with them for alignment.