claude-code - 💡(How to fix) Fix [Feature Request] Add SessionRenamed hook event for external system integration [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/marwantanager/.local/share/claude/versions/2.1.104 (expected in multi-process scenarios)\n at Tc_ (/$bunfs/root/src/entrypoints/cli.js:2836:2153)\n at Se6 (/$bunfs/root/src/entrypoints/cli.js:2836:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-21T23:47:30.889Z"}]

TL;DR

Implementing a "SessionRenamed" hook event is likely to require modifications to the existing codebase to listen for and respond to session rename events.

Guidance

• Review the current hook events available in the system to understand how they are implemented and triggered, which could provide insight into how a "SessionRenamed" event could be integrated.
• Investigate the error message regarding lock acquisition failure, as it might be related to the multi-process scenarios and could impact the implementation of new hook events.
• Consider reaching out to the development team or community for guidance on how to extend the existing hook system, as the addition of a new event like "SessionRenamed" might require collaboration or at least insight into the internal workings of the system.
• Look into the cli.js file mentioned in the error message to understand the context of the lock acquisition failure and how it might be related to the desired functionality.

Example

No specific code example can be provided without more details on the system's architecture and the hook event system's implementation.

Notes

The provided error message seems unrelated to the feature request of adding a "SessionRenamed" hook event but indicates a potential issue with the system's handling of multi-process scenarios. The implementation of such an event would likely require a deeper understanding of the system's internals and possibly modifications to its core functionality.

Recommendation

Apply workaround: Given the lack of a direct way to achieve the desired functionality and the presence of an unrelated error, focusing on finding a workaround or collaborating with the development team to implement the "SessionRenamed" hook event seems like the most viable approach.