[Bug] Crush CLI fails to load configuration in PawWork integrated terminal

[asaprajx]

What happened?

When I launch the crush CLI via the built-in terminal sidebar in PawWork, it fails to load my existing configuration (API keys, MCPs, skills) and prompts me for a new setup. However, running the exact same crush binary in Windows Terminal or the Zed editor sidebar loads my configuration perfectly. Im not sure if the issue is with crush CLI itself or PawWork.

My observations:

Windows Terminal: Works perfectly (loads config/skills/MCPs).
2.
Zed Editor Sidebar: Works perfectly (loads config/skills/MCPs).
3.
PawWork Sidebar: Fails to load config (prompts for setup).

I have verified that $env:USERPROFILE is identical across these terminals, so it does not appear to be a simple path or environment variable mismatch.

Which area seems affected?

Not sure

How much does this affect you?

Minor issue or polish

Steps to reproduce

1. Configure crush CLI in a standard terminal (keys, MCPs, skills).
2. Open PawWork.
3. Open the integrated terminal sidebar in PawWork.
4. Run crush.
5. Observe that it prompts for new setup instead of loading existing config

What did you expect to happen?

crush should load the user configuration consistently regardless of which terminal emulator is hosting the session.

PawWork version

2026.7.3

OS version

Windows 11

Can you reproduce it again?

Yes, every time

Diagnostics

I cannot use my configured tools/skills within the PawWork sidebar, forcing me to duplicate my setup or switch terminals constantly, which is prone to configuration drift.

It's a minor issue, I wanted to use smallar models in crush alongside large models in pawwork for better workflow.

Here are the screenshots.
Windows terminal (opened in pawwork folder)👇

PawWork built-in terminal (opened in pawwork folder)👇