Interface, Execution, and Loop Ownership Are Separate

IDE, ADE, CLI, and web agent describe how a person reaches a product. They do not establish where the code runs or which component owns the agent loop. ADE, short for agentic development environment, is useful vendor language but not a stable comparison category: one product can expose an editor, a terminal agent, a desktop application, and a cloud control surface at the same time.

This catalog therefore uses a controlled interface vocabulary:

Interface	Meaning in this map
cli	A command-line entry point suitable for terminal use or scripting
tui	An interactive terminal interface, including full-screen terminal applications
ide	An editor or IDE integration where the agent works beside source code
desktop	A dedicated native desktop application
web	A browser interface or remote run-monitoring surface
chat	A chat or issue-driven entry point such as Slack, Discord, or a tracker

Treat these as multi-value labels, not mutually exclusive product classes. Then evaluate two independent axes: execution location (local, remote, or hybrid) and loop ownership (runtime, orchestrator, or no loop). For example, Warp Agent is reachable as a standalone CLI with an interactive terminal UI and optional cloud handoff. Its interface does not by itself prove locality, autonomy, sandboxing, or provider independence.