WebUI Console
Current Positioning
According to the latest README, the WebUI is currently used mainly for:
- Dashboard and agent-topology views
- log, memory, and runtime inspection
- OAuth account management
It should no longer be described as a full public runtime-control surface.
Access
The current recommended entrypoint is still through Gateway:
http://<host>:<port>/?token=<gateway.token>That is also the explicit default shown in the current clawgo README.
Main Pages
Dashboard
Used for overall status, including:
- version
- provider runtime info
- recent runtime overview
Agent Topology
The main focus is:
main- local subagents
This is the clearest view of who is coordinating and who is executing.
Config
The current emphasis is viewing and checking configuration.
The docs and README now put canonical config changes back into:
config.jsonAGENT.md
rather than treating the WebUI as the primary edit path.
Provider / OAuth
This is one of the clearest and most stable management surfaces in the current WebUI:
- OAuth login
- account import
- account refresh
- account deletion
- provider runtime status
Logs / Memory / Skills
These pages are mainly for:
- log inspection
- memory-file inspection
- skill browsing and installation
The Most Useful Pages To Open First
If this is your first time opening the WebUI, start with:
- Agent Topology
- Provider OAuth / runtime
- Logs
- Memory
Those pages best reflect the current Agent Runtime state.
Frontend Repository
The frontend source repository is still:
But according to the current clawgo README, the default access model is still Gateway-hosted WebUI.