Description
The Elicitation hook defined in ~/.claude/settings.json never fires
when Claude Code is running inside Warp. The hook is configured correctly
and works as expected in other terminals (confirmed by adding a log line
that is never written to disk).
The Stop hook works correctly in Warp.
Expected behavior
When Claude calls AskUserQuestion, the Elicitation hook should execute
before or alongside the question popup, the same as it does in standard terminals.
Actual behavior
The hook never runs. No log file is created, no command is executed.
Environment
- Claude Code CLI
- Warp terminal with
warp@claude-code-warp plugin enabled
- Windows 11
Hook configuration (settings.json)
{
"hooks": {
"Elicitation": [{ "hooks": [{ "type": "command", "command": "...", "shell": "powershell", "async": false }] }],
"Stop": [{ "hooks": [{ "type": "command", "command": "...", "shell": "powershell", "async": true }] }]
}
}
Description
The
Elicitationhook defined in~/.claude/settings.jsonnever fireswhen Claude Code is running inside Warp. The hook is configured correctly
and works as expected in other terminals (confirmed by adding a log line
that is never written to disk).
The
Stophook works correctly in Warp.Expected behavior
When Claude calls
AskUserQuestion, theElicitationhook should executebefore or alongside the question popup, the same as it does in standard terminals.
Actual behavior
The hook never runs. No log file is created, no command is executed.
Environment
warp@claude-code-warpplugin enabledHook configuration (settings.json)
{
"hooks": {
"Elicitation": [{ "hooks": [{ "type": "command", "command": "...", "shell": "powershell", "async": false }] }],
"Stop": [{ "hooks": [{ "type": "command", "command": "...", "shell": "powershell", "async": true }] }]
}
}