4 ms·

I'm not sure why they insist on code spaces instead of running this inside vs code? Setups/working looks pretty similar to aider [1] that I've been using and l

by Cilvic 2y ago

I'm not sure why they insist on code spaces instead of running this inside vs code? Setups/working looks pretty similar to aider [1] that I've been using and liking, Aider is smaller steps than plandex, but plandex went into some kind of loops a couple of times so I stoped using it for now. [1] https://github.com/paul-gauthier/aider https://github.com/paul-gauthier/aider

lostintangent 2y ago
We definitely intend to explore a VS Code extension in the not too distant future. And we decided to build a web client + integrated cloud terminal, simply because that allowed us to create an experience that is one-click away from an issue, and could be accessed from anywhere and any device (i.e. we’ve deeply optimized CW for mobile, and I do quite a bit of code thinking in that modality). In the meantime, when you open a Codespace from Copilot Workspace, you could open that Codespace in VS Code desktop. And use that as a companion editor to the web client (since we bi-directionally sync file changes between them). But totally agreed that a more integrated VS Code experience will be compelling!
- Cilvic 2y ago
  > simply because that allowed us to create an experience that is one-click away from an issue, That's indeed pretty cool and as you said it's not an either-or. Thanks for providing more background.
danenania 2y ago
> plandex went into some kind of loops a couple of times so I stoped using it for now. Hey, Plandex creator here. I just pushed a release today that includes fixes for exactly this kind of problem - https://github.com/plandex-ai/plandex/releases/tag/cli%2Fv0.9.0 https://github.com/plandex-ai/plandex/releases/tag/cli%2Fv0.... -- Plandex now has a much better 'working memory' that helps it not to go into loops, repeat steps it's already done, or give up too early. I'd love to hear whether it's working better for you now.
- Cilvic 2y ago
  Actually I got the newsletter, will definitely again!

by Cilvic 2y ago

lostintangent 2y ago

We definitely intend to explore a VS Code extension in the not too distant future. And we decided to build a web client + integrated cloud terminal, simply because that allowed us to create an experience that is one-click away from an issue, and could be accessed from anywhere and any device (i.e. we’ve deeply optimized CW for mobile, and I do quite a bit of code thinking in that modality). In the meantime, when you open a Codespace from Copilot Workspace, you could open that Codespace in VS Code desktop. And use that as a companion editor to the web client (since we bi-directionally sync file changes between them). But totally agreed that a more integrated VS Code experience will be compelling!

Cilvic 2y ago
> simply because that allowed us to create an experience that is one-click away from an issue, That's indeed pretty cool and as you said it's not an either-or. Thanks for providing more background.

danenania 2y ago

> plandex went into some kind of loops a couple of times so I stoped using it for now. Hey, Plandex creator here. I just pushed a release today that includes fixes for exactly this kind of problem - https://github.com/plandex-ai/plandex/releases/tag/cli%2Fv0.9.0 https://github.com/plandex-ai/plandex/releases/tag/cli%2Fv0.... -- Plandex now has a much better 'working memory' that helps it not to go into loops, repeat steps it's already done, or give up too early. I'd love to hear whether it's working better for you now.

Cilvic 2y ago
Actually I got the newsletter, will definitely again!