Repository navigation
Extension appending to PATH without delimiter. #1637
Description
Activity
Hi Chris Bode / Hafnium (@hungarian-notation), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Workarounds
- Ensure there’s always a delimiter at the end of your PATH before the extension appends its folder. For example, in your VS Code settings (
settings.json):This guarantees a trailing"terminal.integrated.env.windows": { "PATH": "${env:PATH};" }
;so the debug extension’s script won’t squash into the previous entry.
Next steps
- This appears to be a defect in the Java Debug extension (vscjava.vscode-java-debug@0.59.0). Please file a minimalist repro issue here:
• https://github.com/microsoft/vscode-java-debug/issues/new
No duplicate found among the provided issues.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
Reacted by Chris Bode / Hafnium- Ensure there’s always a delimiter at the end of your PATH before the extension appends its folder. For example, in your VS Code settings (
- This appears to be a defect in the Java Debug extension (vscjava.vscode-java-debug@0.59.0). Please file a minimalist repro issue here:
• https://github.com/microsoft/vscode-java-debug/issues/new
Not enough room in the context window to tell the bot what repo it is commenting in?
- This appears to be a defect in the Java Debug extension (vscjava.vscode-java-debug@0.59.0). Please file a minimalist repro issue here:
- added a commit that references this issue
on May 8, 2026
Version 0.59.0 of this extension breaks the last entry in my PATH variable, as it appends to PATH without a delimiter.
The last entry of my PATH in a vscode terminal with this extension enabled:
In this case it was preventing me from running JReleaser.
I closed my previous issue because the AI temporarily gaslit me into thinking I had misconfigured my terminal, but I have confirmed that this issue persists without any custom
terminal.*settings. I imagine I could fix this by manually adding the delimiter, but that doesn't make this not a defect.