Token Consumption Spike During Ultrathink Command Execution

[slyfox1186]

Bug Description the ultrathink command causes claude to only show the tokens being used count rise way above noramal amount (think above 1200k and beyond!) so this is not right! it shows no output of any kind until it is fully done returning the full results of it's curent 'round' of changes before it gives control back to the user

Environment Info

• Platform: linux
• Terminal: vte-based
• Version: 0.2.122
• Feedback ID: eba7267b-6efb-433c-b993-37c3627f9088

Errors

[{"error":"Error: spawn ENOTDIR\n    at ChildProcess.spawn (node:internal/child_process:420:11)\n    at spawn (node:child_process:762:9)\n    at execFile (node:child_process:351:17)\n    at file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:603:3137\n    at new Promise (<anonymous>)\n    at LU (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:603:3115)\n    at m2 (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:603:3041)\n    at by (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:603:4240)\n    at Object.<anonymous> (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:603:4455)\n    at Object.D [as getRuntimes] (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:491:12878)","timestamp":"2025-05-20T16:18:43.444Z"},{"error":"AbortError: The operation was aborted\n    at abortChildProcess (node:child_process:725:27)\n    at EventTarget.onAbortListener (node:child_process:795:7)\n    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:831:20)\n    at EventTarget.dispatchEvent (node:internal/event_target:766:26)\n    at abortSignal (node:internal/abort_controller:370:10)\n    at AbortController.abort (node:internal/abort_controller:392:5)\n    at Timeout._onTimeout (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:2244:13359)\n    at listOnTimeout (node:internal/timers:581:17)\n    at process.processTimers (node:internal/timers:519:7)","timestamp":"2025-05-20T16:18:53.387Z"}]