Why VSCode v1.107.0 is required?

[makarkotlov]

Is there any reason why the project is based on VSCode v1.107.0? I'm using v1.94.2 and don't plan to update because in later versions Microsoft butchered VSCode's performance with their AI features. I've looked into the codebase and couldn't find any breaking changes that would've prevented the author from using earlier VScode versions. Am I missing something?

P.S. @pablodelucca README states that v1.109.0 is required which contradicts packgae.json that mentions v1.107.0

[pablodelucca]

Hi @makarkotlov, we're just being conservative, given we work with the latest version we have no easy way to test if it works correctly for previous version and thus to ensure it's actually working properly we're lowering the version requirement as we identify people who manage to make it work with previous versions. We've just lowered it to v1.105.0 to allow a bunch of other VS Code forks. Have you tried cloning the repo and lowering the version? If you did and it's all working properly, then we can lower the version requirement in the next release.

[florintimbuc]

Hey @makarkotlov, this is expected behaviour, and after the Extension Development Host is opened you have either to:

1. Look in the bottom panel area (where Terminal/Output/Problems tabs are) for a "Pixel Agents" tab
2. Or Run the command: Cmd+Shift+P -> "Pixel Agents: Show Panel"

Let me know if this works for you

[makarkotlov]

@florintimbuc @pablodelucca it works! thanks a lot for your help!

[florintimbuc]

Great news! @makarkotlov Just to confirm, you're on v1.94.2, right? Would you mind opening a PR with the lowered version and investigating whether any functionality might not work on it? Also, there might be an even lower version we could support. Would you want to dig deeper into that and help us figure it out? :)

[makarkotlov]

@florintimbuc sure thing, investigator's hat on

[makarkotlov]

you're on v1.94.2

yup

[florintimbuc]

Hey @makarkotlov, have you tried cloning the repo and lowering the vscode version in package.json to match yours? It should work, curious if you ran into any issues with that approach

[makarkotlov]

hey @florintimbuc , yeah I might be missing something

[sannatitus]

Hiya, might be a silly question, but I presume higher versions work ok (I'm on 1.112.0)? My agents spawn from the GUI and are pointing to the right source folder however their behaviour is not reactive to the chat (perpetually stuck on idle... subagents spawn though and are also stuck on idle).

[makarkotlov]

@sannatitus for me they start walking and I can assign them to a seat only after a couple of minutes of Claude's work

[florintimbuc]

@sannatitus this will most likely be fixed in #115 once it's merged on main, which also includes various fixes from #183, keep an eye on our main branch for updates or wait for the next release :)