Repository navigation
Ambients Suggestions feature uses UserPromptSubmit hook without Stop hook afterwards #18541
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.415.40636 (1799)
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
I am using Codex CLI/App with Unity Editor. I wrote a custom Unity AI Agent Connector that enables Codex to behave appropriately in a Unity environment, especially in an AI-agentic loop. During agent work, I need to show in the UnityEditor that the task is in progress and its status, and block any user input to prevent interference with the agent work.
For that, I am utilizing 2 hooks: UserPromptSubmit and Stop.
It worked great until the recent CodexApp update that added ambient suggestions feature. It looks like they run after any thread is done and/or archived, and call the UserPromptSubmit hook without Stop at the end. That led to infinite "In progress" task in the Unity Editor
Here is how it looks in the Unity Editor:
My hooks.json:
{
"hooks": {
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "/bin/sh -lc 'dir=\"$PWD\"; while :; do script=\"$dir/.codex/hooks/unity-ai-agent-connector/user_prompt_submit.py\"; if [ -f \"$script\" ]; then exec /usr/bin/python3 \"$script\"; fi; parent=$(dirname \"$dir\"); if [ \"$parent\" = \"$dir\" ]; then printf \"%s\\n\" \"Managed Codex hook script not found: /.codex/hooks/unity-ai-agent-connector/user_prompt_submit.py\" >&2; exit 127; fi; dir=\"$parent\"; done'",
"timeout": 610,
"statusMessage": "Starting Unity task"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "/bin/sh -lc 'dir=\"$PWD\"; while :; do script=\"$dir/.codex/hooks/unity-ai-agent-connector/stop.py\"; if [ -f \"$script\" ]; then exec /usr/bin/python3 \"$script\"; fi; parent=$(dirname \"$dir\"); if [ \"$parent\" = \"$dir\" ]; then printf \"%s\\n\" \"Managed Codex hook script not found: /.codex/hooks/unity-ai-agent-connector/stop.py\" >&2; exit 127; fi; dir=\"$parent\"; done'",
"timeout": 610,
"statusMessage": "Ending Unity task"
}
]
}
]
}
}A few thoughts on how that might be fixed:
- Being able to activate/deactivate Ambients Suggestions feature on the project level (Codex App settings,
config.toml, etc)
— [I doubt you do that, cause it really has a product value] - Don't run hooks for Ambient Suggestion feature
— [still not the best solution] - Fix running
Stophooks
— [will be a workaround, cause it is still not obvious why should I wait for something CodexApp is doing in the background] - Being able to control which hook should be run during Ambient Suggestion. In the
hooks.jsonset something likerunWithAmbientSuggestionsfor each hook (withtrueby default)
Severity:
This thing is really annoying. Thankfully, my connector has a Force End feature, which is a workaround for now
What steps can reproduce the bug?
Already explained in the What issue are you seeing? field
What is the expected behavior?
Already explained in the What issue are you seeing? field
Additional information
No response
Activity
github-actions commentedon Apr 19, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Artein commentedon Apr 19, 2026
It is a separate feature request (which may be a part of the solution for this ticket).
Anyway, this ticket is about the bug in the Ambient Suggestions feature
oxysoft commentedon May 8, 2026
Indexed this hook ticket in the umbrella tracker: #21753
Goal: collect the scattered Codex hook requests and bugs into one parity matrix for Full Claude Code Hook Parity (29+), while preserving this issue as the detailed thread for its specific behavior.
normancates commentedon Oct 1, 2026
Adding a data point from Codex Desktop (codex.exe 0.158.0, Windows), plus what would fix it for hook authors.
What we see:
opening the Desktop app starts ambient suggestion threads and their safety checks, and each one runs the full set of user hooks: SessionStart, UserPromptSubmit, PreToolUse/PostToolUse, Stop and SessionEnd. Memory consolidation threads do too. Nothing in the hook payload says the thread is internal.
Why it matters:
our hooks do things that should happen only in a session the user is actually in:
Suggested fix:
Codex already knows the thread kind internally (ambient_suggestions, ambient_suggestion_safety, memory_consolidation). Please either:
Also: document whether a null transcript_path is a guaranteed signal.