Skip to content

Definition

What is an ADE, an agentic development environment?

An agentic development environment, or ADE, is the workspace you supervise coding agents from, the way an IDE is the workspace you write code in. Its objects are sessions, approvals, diffs and cost rather than files and build targets, and it assumes you still have an editor open somewhere else.

Last updated · Markdown version

IDE objects versus ADE objects

IDEADE
Files and projectsSessions and threads
Build and run configurationsApprovals and tool calls
DebuggerDiffs and the event log
Refactoring toolsCost and plan usage

Why the distinction is useful

Putting agent supervision inside an editor makes it a panel scoped to one open project. Making it a separate surface lets it be about every project at once, which is what actually happens when you run several agents. Neither replaces the other.

What an ADE should not do

  • Hide approvals to look smooth.
  • Summarise tool output instead of showing it.
  • Store credentials it does not need.
  • Pretend a subscription meter reading is a bill.

Frequently asked questions

Does an ADE replace my IDE?

No. It supervises agents. You still write code where you like.

Is Helicon an ADE?

That is the category it is built for: a desktop and web workspace for Muse Code sessions.

Do I need one if I use one agent occasionally?

Probably not. The value appears when you have more threads than you can hold in your head.

Same Muse Code. Same subscription. Better interface. 

Free and MIT licensed. Signed Windows installer, universal macOS DMG, and a web build against a daemon you run.