Definition
What is an ADE (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
| IDE | ADE |
|---|---|
| Files and projects | Sessions and threads |
| Build and run configurations | Approvals and tool calls |
| Debugger | Diffs and the event log |
| Refactoring tools | Cost 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.
Keep reading
- Muse Code desktop appHelicon is a free, open-source desktop app for the Muse Code CLI: Windows installer, macOS DMG, Linux AppImage. Sessions, diffs, approvals and cost in one window.
- Session history and resumeEvery Muse Code session, grouped by project, with full history and one click resume. Sessions started in the muse terminal TUI are discovered and resumable too.
- Running agents in parallelIsolated worktrees, one sidebar, and clear marks for which thread is running, finished, or blocked on you. Plus the cost of all that parallelism, per thread.
- agent approvalsAn approval is the moment an agent asks before acting. The three Muse Code modes, what each one does, and why bypassing them is the wrong optimisation.
- a git worktreeA git worktree is a second working directory for the same repository. It is the cheapest way to stop two coding agents from editing the same files.
- a subagentA subagent is a separate agent a main agent spawns to do part of the work in parallel. Why it saves wall clock time and why it is unreadable in a terminal.
Same Muse Code. Same subscription. Better interface.
Free and MIT licensed. Windows installer, Apple Silicon, Intel and universal macOS DMGs, and a web build against a daemon you run.