When reopening VS Code with the Pi chat sidebar left open from the previous session, the extension gets stuck on an infinite loading screen with the Pi logo.
However, if VS Code is opened:
- with the sidebar closed, or
- with another chat extension opened instead (for example Claude),
then Pi loads correctly afterward.
Environment
- Pi running inside WSL2
- VS Code connection to the WSL via Remote Explorer
- Multiple extensions installed
Additional Information
I can help provide logs or additional debugging information if needed. It would be useful to know where logs are located.
This could help fix the issue either in a future release or through a local workaround.
Thank you for your work on the extension. I was actually considering vibecoding a similar extension myself, but this one already looks very good.
When reopening VS Code with the Pi chat sidebar left open from the previous session, the extension gets stuck on an infinite loading screen with the Pi logo.
However, if VS Code is opened:
then Pi loads correctly afterward.
Environment
Additional Information
I can help provide logs or additional debugging information if needed. It would be useful to know where logs are located.
This could help fix the issue either in a future release or through a local workaround.
Thank you for your work on the extension. I was actually considering vibecoding a similar extension myself, but this one already looks very good.