google-gemini/gemini-cli

[Hooks] Debug logs are too verbose

Closed

#16,629 opened on Jan 14, 2026

View on GitHubContributor guide
 (6 comments) (0 reactions) (1 assignee)TypeScript (13,657 forks)batch import
area/agenthelp wantedkind/bugpriority/p2priority/p3status/bot-triagedstatus/need-information

Repository metrics

Stars
 (103,992 stars)
PR merge metrics
 (Avg merge 4d 2h) (55 merged PRs in 30d)

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

Research direction
Identify the debug logging function in the hooks code and add a flag or condition to limit the verbosity of logged agent trajectories.
Tech stack
typescript
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75