[BUG] Inability to spawn new terminals in a specific working directory with a new version of Claude Code with a prompt.

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

It can osascript the shell in the directory, fine. It can open a new iteration of Claude Code as a worker with a prompt in one bash in a terminal. BUT it cannot open a new directory cd(directory) AND open claude in that directory with a prompt in one bash. It knows how to, And can funnily enough spawn an agent to do it, but now itself! It has worked brilliantly before and is token heavy, but preserves orchestrator context and gives workers max context too, and does not confuse workers. And I can see how and what they code in 10+ shells at once....

What Should Happen?

It should open a new shell in the correct directory and boot claude with a --prompt and let it work naively in that shell, as it has done successfully before.. And by the way.. your report a bug feature in Claude Code CLI failed aswell!

Error Messages/Logs

Steps to Reproduce

I cant recreate it other than what I described and what claude reported. It knows what the command line is, but cannot execute it properly in tandem.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

one before I updated today.

Claude Code Version

v2.1.12

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_