Skip to main content
The iii console is the web UI of ADE: a standalone application that connects to your running engine. It ships as a single binary, published in the registry as ade, that serves the UI and proxies the engine WebSocket on one port (3113 by default). Use it to chat with agents, follow traces and logs, manage the workers in your Compose project, and edit worker configuration. For scripting or agent integration, call worker functions directly.
The legacy iii-console binary is no longer built or released. iii console now only prints a notice that points here, and the command will be removed in an upcoming release. Use the iii console in ADE described on this page instead.

​
Open the console

The console runs next to the engine in your Compose project.
  • Projects created by the installer or by iii project init (see Install) already open the console at http://127.0.0.1:3113 once iii compose --up is running.
  • In any other project, start the project, then add ADE from a second terminal in the same folder:
compose::add resolves ade from the registry, declares it in worker-compose.yaml, and starts it next to the engine. Then open http://127.0.0.1:3113 in your browser. If you run more than one Compose daemon, pass its namespace, for example iii trigger -n dev compose::add worker=ade.

​
What you can do in it

The console is a workspace of tabs and panes. Built-in screens are Chat, Traces, and Workers; workers you install can add their own pages to it.

​
Chat

Chat with an agent running on the harness worker. Add the agent stack with:
The first time you open the console on a machine, a setup wizard helps you connect a model provider. In the composer you can pick a model, mention any registered function or a file in the working directory with @, and approve or deny function calls that need approval. Each conversation links to its traces.

​
Traces

An OpenTelemetry explorer for the engine’s traces and logs. Spans stream in live. You can filter by status, time, duration, and attributes, group results, and open a trace as a timeline or a waterfall. A span’s detail shows its attributes, events, errors, logs, and context.
Traces and logs come from the iii-observability worker. The console reads the engine’s local storage, so configure traces with exporter: memory or exporter: both, and logs with logs_exporter: memory or logs_exporter: both. Use both when you also export to an external OTLP collector. See Observability.

​
Workers

Lists every worker that the Compose daemon runs, and every worker connected to the engine outside Compose. For a Compose worker you can follow its logs, change its version or source, edit its settings (run script, start order, environment), and see the functions it registered. Add worker declares a new worker from the registry or a local directory. Changes go through the daemon’s own compose::* functions; see Compose.

​
Settings

Settings lists the configuration entries of your workers and lets you edit and save them. See Configuration.

​
Configure the console

The console registers its own console entry with the configuration worker. Its http_port setting (default 3113) moves the listener without a restart. You can edit the entry under Settings, or set it like any other configuration entry. For every option, see the ADE worker README.