Drive It From the Browser
Using the embedded web dashboard instead of the TUI, and where to read next.
Or drive it from the browser
The daemon serves a dashboard from the same port the API runs on. With agen running, open:
http://127.0.0.1:17989
The page is embedded in the binary, so nothing is fetched from a remote host and nothing leaves your machine. Since v1.0.1 the third-party libraries it uses are downloaded once at daemon startup into ~/.config/agenvoy/vendor/ and served locally, and a service worker precaches the rest — so the dashboard keeps working with no network at all. Sessions, chat, schedules, models, MCP servers and roles are all editable there (rules were renamed roles in v1.1.0; operator notes were removed in v1.0.23). Since v1.0.12 the System settings panel also holds the Telegram / Discord / admin channel setup (moved out of its own page), launch-on-login, reply language, the output directory with an open dir shortcut, and a version row that compares the running build against the latest GitHub release and can start agen update in a terminal window. The Other group below it holds the Doc, License and Source entries; the last two are the notices AGPL-3.0 §7(b) requires the interface to keep (v1.0.16) — see License.
To run one request without the TUI, post it:
curl -sS -H 'Content-Type: application/json' \
-d '{"content":"summarize the latest changes in main.go"}' \
http://127.0.0.1:17989/v1/send
Without session_id the request runs in a new temporary session; model and skill are optional. There is no allow_all field.
Next steps
- Sessions & Agents — sessions, agent routing, and subagents
- Execution Engine — the iteration loop and three-pass tool dispatch
- Providers — supported LLM backends and the dispatcher model
- MCP Client — plug in external tool servers
- CLI Commands — full command list
[!NOTE] This document was auto-generated by Claude after reading the full source code.