Repeated sporadic hook timeouts with codex
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 178
Description
What happened?
• UserPromptSubmit hook (failed)
error: hook timed out after 30s
• SessionStart hook (failed)
error: hook timed out after 30s
• Stop hook (failed)
error: hook timed out after 30s
Steps to reproduce
- start using codex with entire enabled and configured
Entire CLI version
❯ entire version Entire CLI 0.5.5 (90bb1c50) Go version: go1.26.2 OS/Arch: darwin/arm64
OS and architecture
Darwin 25.3.0 arm64
Agent
codex-cli 0.120.0
Terminal
ITerm2
Logs / debug output
https://gist.github.com/ksquarekumar/80103708b72b5c2c55a8d58449f4e742
This one failed on UserPromptSubmit, others worked though Stop almost failed too
› Hi
• SessionStart hook (completed)
warning: Powered by Entire: This conversation will be linked to your next commit. 1 other active conversation(s) in this workspace will also be included. Use 'entire status' for more information.
• UserPromptSubmit hook (failed)
error: hook timed out after 30s
• I’m thinking about how to approach this casual conversation. Since there’s no need for me to browse for information, I can focus on keeping it simple. A friendly greeting should suffice, and I could offer help if
needed. There’s really no reason to be overly verbose here; I want to keep my response direct and concise while still being friendly. So, I’ll just stick to a straightforward greeting!
• Hi. What do you need help with?
Additional context
Where is the timeout happening at ?
Anything wrong in my setup ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the UserPromptSubmit, SessionStart, and Stop hook execution paths, using the linked gist and the reported Entire CLI 0.5.5 environment as the reproduction context. Determine where the 30-second timeout is reached and whether the behavior can be reproduced with codex-cli 0.120.0 on Darwin arm64. Done means the timeout cause is identified and the affected hook behavior is corrected or clearly diagnosed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100