Modo was also really good, ahead of its time in many respects. Excellent UX, the material system was quite good, especially for rapid prototyping.
VerifiedReports 1 days ago [-]
Look out, you're going to get downvoted by the fact-averse.
VerifiedReports 12 hours ago [-]
See?
gbro3n 1 days ago [-]
This looks great. Building right into the editor looks like a solid way to go. I built "Agent Kanban" (anextension) for VS Code to enforce a similar "plan, tasks, implement" flow as you describe. That flow is really powerful for getting solid Agentic coding results. My tool went the route of encouraging the model via augmenting AGENTS.md and having the Kanban task file be markdown that the user and agent converse in (with some support for git worktrees which helps when running multiple sessions in parallel): https://www.appsoftware.com/blog/introducing-vs-code-agent-k...
savolai 1 days ago [-]
I just posted something similar but with Obsidian Kanban plugin .md files:
Can subagents work on multiple branchs at the sametime (in a sandbox or some other way)?
This is a major pain atm with any IDE, they all fight over the same git cmd instance and make a mess out of it. I have a custom setup for this but would like some more integrated way of solving this.
ElFitz 1 days ago [-]
Should be doable with worktrees. Claude Code has a flag for that, others probably do too.
chrisweekly 1 days ago [-]
Yes, this; git worktree is a pretty standard solution, straightforward to leverage in any IDE or AI harness worth its salt.
xkbear89 1 days ago [-]
[dead]
chappyasel 1 days ago [-]
[dead]
lightbulbish 1 days ago [-]
A visual demo beyond entering an api key would be useful. A picture says a thousand words. I did not feel inclined to read all of the readme, but when i saw people here talking about mission control I went back one more time.
lnenad 1 days ago [-]
Do you feel like you need a demo for yet another VSC vibecoded clone?
digitaltrees 1 days ago [-]
I have settled on the same approach as you except I have the agent create a roadmap.md in an /agile folder with numbered epics containing sprints, user stories and other context.
crefiz 1 days ago [-]
Why? Like legit question, did you do it for the academy or are you genuinely trying to add yet another (agentic) IDE into the market?
hahooh 11 hours ago [-]
maybe for fun?
simple10 2 days ago [-]
Really cool. I've been building a mission control system (multi agent orchestration) that follows very similar patterns of spec driven development, steering, and task management. Having this baked into an IDE is a great idea.
For observability, would be amazing to have session replay or at least session exploration built in. Kinda like git history but tied to tasks and tool use instead of file diffs.
jv22222 2 days ago [-]
How does modo help vs using a skill or claud.md that says to always do this?
Not a critique just giving you a chance to sell it :)
moropex 1 days ago [-]
yeah this is my question too. a good CLAUDE.md with some structure goes a long way already
esafak 2 days ago [-]
What did you learn?
neurworlds 1 days ago [-]
curious how Modo handles multi-file edits across a monorepo, that's where most tools fall apart for me
https://news.ycombinator.com/item?id=47659511
This is a major pain atm with any IDE, they all fight over the same git cmd instance and make a mess out of it. I have a custom setup for this but would like some more integrated way of solving this.
For observability, would be amazing to have session replay or at least session exploration built in. Kinda like git history but tied to tasks and tool use instead of file diffs.
Not a critique just giving you a chance to sell it :)
https://www.foundry.com/news-and-awards/foundry-winds-down-m...