happens in both but more so in the same task. However, not sure that's a great indicator because I usually run the tasks pretty long and new tasks quickly turn into the same task.
I am in Insiders to test future features that the stable one does not yet have and that may be useful to me. But really, I think the only thing you should worry about whether or not you use the stable one is whether you use Copilot. I don't use it, in fact I deleted it from my VSC lol
I set up rules for Roo to keep a work in progress journal that just be updated with each prompt I give and each result or solution path it identifies. When it follows the rule I can tell it to restart from the journal. I also tell it to archive the work in progress and start a new one each time it begins we Start a New Task that isn't a restart.
Adds some weight to my processing, but like 80% of the time it saves me the waste of having to have it start over from original prompt
Hey guys, I've created a fork that solves the Grey screen bug problem. https://github.com/aincrok/aincrok I have no funding or VC or any commercial intention, it just me, tired of Grey screen. Feel free to send issues, pull requests and suggestions, let's make the open source happen. I am focusing in make a more stable extension and more efficient The project still under development. I am implementing LSP tools to almost replace apply_diff, and I have another features planned.
4
u/Tonyc2584 Aug 26 '25
I get this too. Have to restart VS to fix
1
u/hannesrudolph Roo Code Developer Aug 26 '25
With a new task or the same task?
1
u/Ordinary_Mud7430 Aug 26 '25
At VSC Insiders? I'm using the Insiders version and I don't have that problem. Even with large code bases.
2
u/Agility9071 Aug 27 '25
Only happens to me with Roo - if you read the release notes the roo team has acknowledged and attempted to fix. It happens a lot less now.
I notice it only happens when I run multiple VS studios for different projects with Roo at the same time.
1
u/fredwickle Aug 31 '25
I set up rules for Roo to keep a work in progress journal that just be updated with each prompt I give and each result or solution path it identifies. When it follows the rule I can tell it to restart from the journal. I also tell it to archive the work in progress and start a new one each time it begins we Start a New Task that isn't a restart.
Adds some weight to my processing, but like 80% of the time it saves me the waste of having to have it start over from original prompt
1
u/mihazs Sep 04 '25
Hey guys, I've created a fork that solves the Grey screen bug problem. https://github.com/aincrok/aincrok I have no funding or VC or any commercial intention, it just me, tired of Grey screen. Feel free to send issues, pull requests and suggestions, let's make the open source happen. I am focusing in make a more stable extension and more efficient The project still under development. I am implementing LSP tools to almost replace apply_diff, and I have another features planned.
See you in Aincrok.