[BUG] RunVsAgent vscode-powershell integrations break Jetbrains Powershell terminal #1752

Activity

1. aGitForEveryone

   added

   bugSomething isn't workingSomething isn't working

   on Sep 22, 2026
2. PierrunoYT commented on Sep 28, 2026

   

   PierrunoYT

   on Sep 28, 2026

   Contributor

   More actions

   Working on it!
3. PierrunoYT commented on Sep 28, 2026

   

   PierrunoYT

   on Sep 28, 2026

   Contributor

   More actions

   I verified both findings. Neither is in this repo: the profile ships from Zoo-Code-Org/Zoo-Code-Jetbrains. WeCoderTerminalCustomizer.kt copies run-vs-agent-shell-integrations/vscode-powershell/profile.ps1 to ~/.run-vs-agent-shell-integrations/ and launches PowerShell terminals with it.

   1. Parse error: the cause is file encoding, not ]

   Parsing the shipped profile.ps1 with PowerShell's own parser reproduces the report exactly:

   Variant	Windows PowerShell 5.1	PowerShell 7
   Shipped file	2 errors: line 89 col 21 and line 144, unexpected token ]	0 errors
   Kilo's fix (double → single quotes, 2fdced3)	1 error, moved to line 154	0 errors
   Shipped file saved with a UTF-8 BOM	0 errors	0 errors
   Shipped file with the emoji removed	0 errors	0 errors

   profile.ps1 is UTF-8 without a BOM, and Windows PowerShell 5.1 reads BOM-less scripts as Windows-1252. The emoji on lines 9, 10, 28 and 182 (📁, 🔑, 🔍) contain the bytes 0x93/0x94, which Windows-1252 decodes as curly double quotes. PowerShell treats those as string delimiters, so string boundaries drift through the rest of the file and the error surfaces at the ] on line 89. That's why Kilo's quote swap only moves the error. Saving the file with a BOM (as JetBrains' own powershell-integration.ps1 does) or keeping it ASCII-only fixes it. PowerShell 7 reads BOM-less files as UTF-8, which is why only 5.1 users see this.

   2. Virtual environment not activated

   PyCharm starts PowerShell with -File <IDE>/plugins/terminal/shell-integrations/powershell/powershell-integration.ps1. That script applies the _INTELLIJ_FORCE_* variables and runs $Env:JEDITERM_SOURCE, which is the venv activate script.

   injectPowerShellScript replaces that -File argument with our profile.ps1 and stores the original path in ORIGINAL_POWERSHELL_SCRIPT, but profile.ps1 never reads that variable. The JetBrains script therefore never runs, and neither does venv activation.

   A simulated launch (stand-in scripts, Windows PowerShell 5.1) confirms it:

   • -File jb-integration.ps1 → venv activated
   • -File profile.ps1 with ORIGINAL_POWERSHELL_SCRIPT set → nothing runs

   Proposed fix (in Zoo-Code-Jetbrains)

   1. Save profile.ps1 (and diagnose.ps1) as UTF-8 with BOM, or remove the emoji.
   2. After the user profile is loaded, run the script the -File swap replaced:

      if ($env:ORIGINAL_POWERSHELL_SCRIPT -and (Test-Path -LiteralPath $env:ORIGINAL_POWERSHELL_SCRIPT)) {
      	. $env:ORIGINAL_POWERSHELL_SCRIPT
      }
      $env:ORIGINAL_POWERSHELL_SCRIPT = $null

   With both changes, the simulated launch parses cleanly in 5.1 and activates the venv again. This was only tested with stand-in scripts, not in a real PyCharm. The real JetBrains script also installs its own prompt hooks, so how they interact with our Prompt override still needs checking in the IDE.

   🎉React with 🎉1Reacted by Tobias Van Damme
4. aGitForEveryone commented on Sep 28, 2026

   

   aGitForEveryone

   on Sep 28, 2026

   Author

   More actions

   Awesome analysis! Thanks for picking it up.
5. aGitForEveryone commented on Oct 22, 2026

   

   aGitForEveryone

   on Oct 22, 2026

   Last edited by aGitForEveryone

   Author

   More actions

   Bumping this issue again. Part of it was addressed in Zoo-Code-Org/Zoo-Code-Jetbrains#10. However, the part where it runs PyCharms activation scripts was not added. I wrote a comment on that in this issue: Zoo-Code-Org/Zoo-Code-Jetbrains#7.

   Can the branch that activates Pycharm/JetBrains activation scripts be added?
6. aGitForEveryone commented on Oct 27, 2026

   

   aGitForEveryone

   on Oct 27, 2026

   Author

   More actions

   Issue has been solved in Jetbrains repo.
7. aGitForEveryone

   closed this as completedon Oct 27, 2026