claude-code - 💡(How to fix) Fix [Feature Request] Surface hook identity in async hook completion messages [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/badawi/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T10:39:16.767Z"},{"error":"AxiosError: Request failed with status code 404\n at zl (/$bunfs/root/src/entrypoints/cli.js:114:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:119:12696)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:121:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T10:43:17.928Z"},{"error":"MaxFileReadTokenExceededError: File content (30602 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at qC7 (/$bunfs/root/src/entrypoints/cli.js:4789:12701)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T10:43:22.073Z"}]

TL;DR

To address the issue of generic async hook completion messages, consider adding a unique identifier or label to each hook in the settings.json file.

Guidance

• Review the proposed solutions in the issue description, specifically adding a "name" field to hook entries in settings.json, to provide a clear identifier for each hook.
• Consider the benefits of including the hook command or a derived label in the completion message for easier debugging and performance monitoring.
• Evaluate the trade-offs between the two proposed solutions: (a) including the hook command in the completion line, and (b) adding an optional name/label field in settings.json.
• Investigate how the harness currently handles async hook completion messages and how it can be modified to include the proposed changes.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue highlights the need for better debugging and performance monitoring capabilities for async hooks. The proposed solutions aim to address this by providing a clear identifier for each hook in the completion message.

Recommendation

Apply workaround (b) by adding an optional name/label field to hook entries in settings.json, as it provides a flexible and scalable solution for identifying and debugging async hooks.