empty
Resolved 💬 2 comments Opened May 22, 2026 by ZardLi1115 Closed May 25, 2026
Hi maintainers — I’d like to help with this, but will wait for explicit approval before opening a PR.
Proposed plan:
- Reproduce or trace the WSL-specific shell snapshot startup path in the Claude Code CLI harness.
- Identify the smallest failing boundary, likely around bash/shell detection, environment capture, path handling, or snapshot initialization on WSL.
- Add a focused regression test or fixture that covers the failing WSL shell snapshot case without requiring broad platform-specific CI changes.
- Implement the minimal fix in the harness startup/snapshot logic, keeping behavior unchanged for non-WSL platforms.
- Validate with the relevant unit tests and any available CLI/harness smoke tests.
Scope limits:
- I will keep the PR small and targeted to one bug fix.
- I will avoid unrelated refactors or behavior changes.
- If the fix requires a larger design decision or unavailable private harness details, I’ll report findings instead of pushing a speculative change.
Would you be open to a PR following this plan?
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗