Simon Massey

Verdent Deck moves beyond the "IDE Agent" or "CI Agent" model to deliver a ground-breaking DevX. I am confident that this software is the most underrated tool on the market. You would be unwise to overlook it.

There is an elephant in the room that is harming AI adoption outside of the West Coast bubble:

• You wouldn't want to share one IDE instance across a team of several people.

• You wouldn't want to be working on concurrent high-impact move-fast features with team members who only show a pair of eyes on a GitHub PR, then send back a massive response after a dozen minutes.

• To achieve true agent parallelism, you need to launch many IDEs in cloud codespaces, flip between multiple local IDEs, and manage many PRs and cloud containers across different browser tabs.

If you are pushing the limits, you will know that feeling of being lost after a reboot as you try to reconnect with all the in-flight work. Have you ever felt like apologising to an agent because you lost track of their work and they are now too far behind? Me too. 

That problem isn't apparent until you see an alternative; Verdent Deck is a breakthrough alternative. It provides a Developer Experience that:

• Is task- and outcome-focused; yet the development is local and immediate especially.

• The details no longer dominate, yet they are only one click away. Verdent Deck, and it provides a button to open it in any and all of the IDEs I have installed. This is a stroke of pure genius.

• There is simply more space to breath with less settings to twiddle. Finally a left-to-right layout that makes sense as you drip down into the details.

• You can do more things in parallel; especially when assigning Tasks to git-worktrees.

The power of Verdent Deck is that I can now see the big picture. I can run more tasks in parallel without getting lost when context switching. That wasn't the case with all the other tools I tried over the past year.

The support for this app is also exceptional. I used an early release and ran into some glitches as I ramped up to many parallel tasks across multiple projects. The Verdent AI Team responded very quickly.

Grab a copy today and challenge yourself to do something more ambitious than you thought possible. For people ready to move beyond traditional IDEs and CI Agents, Verdent Deck may be a perfect fit.

"Verdie: The Spirit Of New Growth"

N/A - it is currently an early release so still in active development.

I use cursor (and copilot, and continue, and openhands, and....) yet as per my review you end up single threading in a single IDE else doing handoffs via PRs. There is nothing wrong with that way of working in many contexts but it misses out on a whole 3rd dimension that Verdent Deck explore. I am not saying that it replaces the other ways of working; but I am saying that the other ways of working cannot replace Verdent Deck!

yes. totally.

no you can kill it but not pause it as it is looking to be autonomous to a task. you should assign the Task to a git-worktree so that you can context switch. if you stop them all state is local you can resume them by just asking them to continue.

You can pick which model is doing the coding and which is doing the testing. Critically you can use different model families across di

N/A

Agents are local. If you lose connectivity mid task or reboot their thinking logic has been logged and you can just chat to them to say to continue and they have the full local context and they carry on where they left off.