area/agenthelp wantedkind/bugpriority/p2priority/p3status/bot-triagedstatus/need-information
倉庫指標
- 星標
- (103,992 顆星)
- PR 合併指標
- (平均合併 4天 2小時) (30 天內合併 55 個 PR)
描述
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