I had CC analyze the Windows ver of Claudia.
Issues Fixed (on my laptop)
- Production Build Process Restrictions - The code artificially disabled process spawning in production builds with
#[cfg(not(debug_assertions))] guards, making it impossible for the built app to launch Claude Code
- Windows Command Detection - Used Unix which command instead of Windows where command, preventing binary detection
- Missing Windows Environment Variables - Added USERPROFILE, APPDATA, LOCALAPPDATA, TEMP, TMP for proper Windows environment
inheritance
Remaining Issues
- Process Communication Breakdown - The built app can find Claude Code but hangs when executing prompts, suggesting a
fundamental issue with how Tauri handles process I/O in production vs development
- Environment Context Loss - The built app likely doesn't inherit the same shell environment as when you run Claude Code
directly from command line
- Authentication/Config Access - Claude Code may not be able to access its stored authentication when launched from the built
app context
- Working Directory Issues - The project_path passed to Claude Code may not resolve correctly in the built app environment
I had CC analyze the Windows ver of Claudia.
Issues Fixed (on my laptop)
#[cfg(not(debug_assertions))] guards, making it impossible for the built app to launch Claude Code
inheritance
Remaining Issues
fundamental issue with how Tauri handles process I/O in production vs development
directly from command line
app context