PowerShell Terminal broken: Unexpected token: ']' #7

Activity

1. olconstant commented on Sep 25, 2026

   

   olconstant

   on Sep 25, 2026

   Author

   More actions

   Any plan to fix this bug? I'm stuck with Cline because of this bug. Having a working Terminal on IDE is important. Thanks.
2. olconstant

   changed the title [-]PowerShell terminal is reporting ] as unexpected[/-] [+]PowerShell Terminal broken: Unexpected token: ']'[/+] on Sep 25, 2026
3. aGitForEveryone commented on Oct 5, 2026

   

   aGitForEveryone

   on Oct 5, 2026

   More actions

   I opened an issue on this on the original Zoo Code repo: Zoo-Code-Org/Zoo-Code#1752. Some initial investigation was done on the issue. Hope that it gets translated into a bugfix soon.

   👍React with 👍1Reacted by Olivier Constant
4. aGitForEveryone commented on Oct 22, 2026

   

   aGitForEveryone

   on Oct 22, 2026

   Last edited by aGitForEveryone

   More actions

   I want to highlight this issue again. In PR #10 step 1 was taken to fix compatibility issues, the emojis that were causing an issue are removed. thanks!

   However, a second part is still not fixed: running PyCharms activation scripts. The response in Zoo-Code-Org/Zoo-Code#1752 suggests as a solution to add in ZooCode's profile.ps1:

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

   I tried that on my own system. I added the snippet under the section # Load user's original PowerShell profile if shell integration was injected. So the code becomes:

   # Load user's original PowerShell profile if shell integration was injected
   if ($env:VSCODE_INJECTION -eq "1") {
   	# Source user's original profile if it exists
   	$UserProfile = $PROFILE.CurrentUserCurrentHost
   	if (Test-Path $UserProfile) {
   		. $UserProfile
   	}
   	$env:VSCODE_INJECTION = $null
   }
   
   $pyCharmScript = $env:ORIGINAL_POWERSHELL_SCRIPT
   if ($pyCharmScript -and (Test-Path -LiteralPath $pyCharmScript)) {
       . $pyCharmScript
   }
   $env:ORIGINAL_POWERSHELL_SCRIPT = $null
   
   $Global:__VSCodeOriginalPrompt = $function:Prompt
   $Global:__LastHistoryId = -1
   $Global:__VSCodeIsInExecution = $false
   

   On my system this change reactivates the virtual environment, i.e. solves the issue. You can try this in a live PyCharm window with the ZooCode plugin enabled. In the default state, the virtual environment is not activated. Next, open C:\Users\<user>\.run-vs-agent-shell-integrations\vscode-powershell\profile.ps1, replace the code as above. After saving the file, open a new PowerShell instance in PyCharm. You should see that the active interpreter is now correctly activated.

   Can this extra section be added to the profile.ps1 script?
5. aGitForEveryone commented on Oct 22, 2026

   

   aGitForEveryone

   on Oct 22, 2026

   More actions

   To already make a headstart in solving this issue, I made a PR: #11.

   Note that I only verified this change in PyCharm as that is the only JetBrains tool that is use. Do you have tests to check other JetBrains IDEs?