area/agenthelp wantedkind/bugpriority/p2priority/p3status/bot-triagedstatus/need-information
Repository metrics
- Stars
- (103,992 個のスター)
- PR merge metrics
- (平均マージ 4d 2h) (30d で 55 merged PRs)
説明
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