Philosophy
We are entering the era of the Integrated Overview Environment (IOE). The tools of the past were built for typists; the tools of the future are built for directors.
Why IOE?
The "D" in IDE (Development) implies manual labor: the act of typing. As AI agents take over the "development" of code, the human role shifts. "Overview" (the "O" in IOE) acknowledges this transition. It implies high-level orchestration, pattern recognition and strategic decision-making.
Environment vs. Editor
An IDE is a tool you open to change a file. An IOE is a space you inhabit to manage a system. Dispatch isn't just a text box; it's a mission control center | an environment where you observe and direct autonomous agents.
Directing vs. Typing
In an IOE, the human provides the vision, while the agent provides the implementation. You aren't "coding"; you are Synthesizing. You aren't "debugging"; you are Validating.
Context as Currency
In the age of LLMs, context is the most precious resource. An IOE is designed to manage, compact and hand off context between specialized agents, ensuring that "state" is never lost across long sessions.
Mission Control
Dispatch's 3D "Floor" view is the physical manifestation of this philosophy. It's a cockpit where goals decompose into specs, and specs into agent runs. You aren't looking at lines of code; you're looking at a live stream of reasoning, telemetry and progress.
"The best way to build the future is to stop writing it and start directing it."