I like that Verdent generates subtasks, their dependencies, and even the related test cases. I can review, accept, or adjust this plan before any code changes are made.
I also see Verdent has a desktop option. In which cases do you recommend using it versus the VS Code extension?
Verdent Deck (the desktop app) could be considered as a recommended way to start. You can have multiple agents run in parallel, code review, code diff explained, etc. Then if needed you can jump into VS Code and work on specific parts with our extension.
I normally just use CLIs and a single Markdown file but I found Verdent useful as it helps to have a central place to refer back to the chats and coding tasks.
We strongly believe that the future will be orchestrated, and in that future harnessing the multi agent workflows will be crucial. But yes, sometimes simple solutions work.
I like that Verdent generates subtasks, their dependencies, and even the related test cases. I can review, accept, or adjust this plan before any code changes are made.
I also see Verdent has a desktop option. In which cases do you recommend using it versus the VS Code extension?
Verdent Deck (the desktop app) could be considered as a recommended way to start. You can have multiple agents run in parallel, code review, code diff explained, etc. Then if needed you can jump into VS Code and work on specific parts with our extension.
I normally just use CLIs and a single Markdown file but I found Verdent useful as it helps to have a central place to refer back to the chats and coding tasks.
We strongly believe that the future will be orchestrated, and in that future harnessing the multi agent workflows will be crucial. But yes, sometimes simple solutions work.
I used Verdent in Beta, and it worked miracles in getting my app from 0 to fully functional. Absolutely amazing product! Congrats Verdent team.
Thanks, we have invested lot of effort into making the whole experience meaningful.