google-gemini/gemini-cli

[Hooks] Debug logs are too verbose

Open

#16629 opened on Jan 14, 2026

View on GitHub
 (5 comments) (0 reactions) (1 assignee)TypeScript (103,992 stars) (13,657 forks)batch import
area/agenthelp wantedkind/bugpriority/p2priority/p3status/bot-triaged

Description

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

Contributor guide

Tech stack
typescript
Domain
clideveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with hooks systemUnderstanding of debug logs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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.