Show HN: I left VSCode to build an IDE to handle many projects/agents workflow

[davideweaver]

VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less.

So I built my own IDE around that workflow. Terminals are a first-class citizen, every project stays alive in the background with visual statuses. Close the workspace and come back weeks later, everything is still in its place. I've been using it for weeks and it's a big productivity boost.

The idea is a super tight core with a robust extension SDK. Features are built as extensions and are optional. Extensions can easily be built with a coding agent and shared in a registry. All open source.

There's many great TUI apps that have similar features, but this is built for someone that loves VSCode. Please try it out and send feedback.

[azaras]

I understood that you was in the VSCode dev team.

"I left using VSCode to build an IDE ..." is a most honest claim.

[davideweaver]

No, sorry. I wasn't involved with the VSCode team. I was just a hard-core user. Bad wording :(

[joshka]

Consider optimizing your demo for laptop user screen sizes and checking contrast of all elements. A lot of things on the demo are difficult to read fast due to low contrast, which makes animations using them less useful to show off what is actually happening.

[davideweaver]

Will do. Thanks for the feedback

[bombcar]

How do you solve the “many agents one git repo” problem?

[davideweaver]

yes, worktrees can manage that. there is full support for worktrees in Silo, whether the agent creates them or you manually create them for the workspace. worktrees show up in the file explorer and the git explorer

[two_handfuls]

Worktrees I suppose?