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...
Interesting approach building this into the editor directly.
In my trials, I've noticed testing AI coding agents on real startup tasks - I stress tested an AI Co-Founder : the biggest failure mode isn't code quality — it's sycophancy. The agent agrees with your wrong assumptions instead of pushing back. Any plan to build guardrails against that into Modo's "plan, tasks, implement" flow? Seems like the planning stage would be the right place to catch it.
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.
that can be definitely implemented, I've also similar idea in another repo in my GitHub called ckpt you can check if you are interested but definitely that's sth that can be added ofc
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.
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.
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.
Modo was a DCC software: https://en.wikipedia.org/wiki/Modo_(software)
wow that's a really nice looking icon
Modo was also really good, ahead of its time in many respects. Excellent UX, the material system was quite good, especially for rapid prototyping.
[flagged]
See?
Their comment is literally #1 in this comment section. Please don't complain about downvotes, especially someone elses.
"Literally" #1? As opposed to what?
And why not?
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...
I just posted something similar but with Obsidian Kanban plugin .md files:
https://news.ycombinator.com/item?id=47659511
Interesting approach building this into the editor directly.
In my trials, I've noticed testing AI coding agents on real startup tasks - I stress tested an AI Co-Founder : the biggest failure mode isn't code quality — it's sycophancy. The agent agrees with your wrong assumptions instead of pushing back. Any plan to build guardrails against that into Modo's "plan, tasks, implement" flow? Seems like the planning stage would be the right place to catch it.
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.
Should be doable with worktrees. Claude Code has a flag for that, others probably do too.
Yes, this; git worktree is a pretty standard solution, straightforward to leverage in any IDE or AI harness worth its salt.
that can be definitely implemented, I've also similar idea in another repo in my GitHub called ckpt you can check if you are interested but definitely that's sth that can be added ofc
[dead]
[dead]
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.
Do you feel like you need a demo for yet another VSC vibecoded clone?
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.
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?
maybe for fun?
for fun :)
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.
What did you learn?
a lot, most important is there is still to much to be added to the space of agentic coding
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 :)
yeah this is my question too. a good CLAUDE.md with some structure goes a long way already
curious how Modo handles multi-file edits across a monorepo, that's where most tools fall apart for me
really didn't work yet on that but might do if I get more time. there are a lot of ideas to be implemented
[dead]
[dead]
[dead]
[dead]
[dead]
[flagged]
[flagged]
[dead]
[dead]
[flagged]
was *
https://www.foundry.com/news-and-awards/foundry-winds-down-m...
for almost 20 years.