Idea for Cursor: Agent orchestration layer on top of the IDE (vibe concept + demo)

Discussions
1

I’m a product engineer / team lead, been building production workflows around AI coding agents for real-world development: not just codegen, but task breakdown, refactors, migrations, and ongoing maintenance.

While using Cursor and other tools, I ended up with a “vibe‑level” idea for an agent orchestration layer on top of the IDE. In short:

  • agents don’t just reply in chat, they act as structured workflow units;

  • there are explicit tasks, statuses, retries, fallbacks, logs, and metrics;

  • multiple agents can be combined (planner, implementer, reviewer) and wired into real dev processes (backlog, CI, code review, etc.).

I’ve built a small prototype on top of existing APIs (CLI/HTTP + LLMs) and I see a few places where this could complement Cursor:

  • more transparent orchestration for complex, multi-step, multi-file tasks;

  • reusable “context bundles” / agent configs that can be shared across projects and teams;

  • better observability of what agents did, with which prompts, and what the outcome was.

I’d be happy to:

  • show a short demo (video or live),

  • share what already runs in production for us vs what’s still experimental,

  • discuss whether this direction aligns with how the Cursor team thinks about agents.

Questions to the community and the Cursor team:

  • Would you find a more explicit agent orchestration layer on top of the IDE useful?

  • Which scenarios would you prioritize first (refactoring, large migrations, legacy maintenance, onboarding, etc.)?

If someone from the Cursor team sees this — I’d really appreciate your feedback and would love to explore this idea in more detail.

Thanks!

3

I’ve seen this concept in oh-my-claude and oh-my-opencode. So, I went ahead and started making a Cursor native approach.

My suggestion:
Don’t ask, just do it. Share it, make it known!

Let me know what you think of my setup. I’m currently working on the next version with a massive overhaul, including features in cursor that are not documented!

I’d love to try your setup as well. Feel free to copy anything from mine, this is open-source!

4

Here’s what I managed to build with Claude all by myself in just 4 days. If you want, feel free to fork it—my project is open-source too!

5

WOW! I’m impressed by the demo! https://vibe-ashy-nine.vercel.app/
Great work.

6

With the way things are going, there’s a chance here for Cursor to “rebuild” the IDE

Complete rewrite in a native language Zig, Rust, Go, whatever. Creating a UI similar to Opencode’s GUI, Codex, etc. In here you deal more with agents and orchestration. Provide easier tooling for setting up these workflows and agents within this view

Then have it open the Electron based IDE within the GUI, via panes/tabs/however when needed

===

Obviously keep the old IDE around for those that prefer it