Vi Dashboard — The Admin Panel Interface
Vi runs on the Hermes-Agent engine, container ID hm-3 (Rose and Ada are OpenClaw on oc-1 / oc-2). Inside the Admin Panel, Vi has its own tab for monitoring and configuration.
Want to know what Vi does? See Vi — Technical Advisor. This page focuses on how to drive the Vi Dashboard inside the Admin Panel.
Container Info
| Property | Value |
|---|---|
| Container Name | hm-3 |
| Engine | Hermes-Agent |
| Permission Scope | Container-isolated + code-execution sandbox |
| Hermes UI URL | https://{your-prefix}-3.realvco.com/ |
Four Sub-Tabs
Vi Dashboard has four sub-tabs, matching the structure of the Rose and Ada dashboards.
[Screenshot: Vi Dashboard overview with Overview / Activity / Usage / Settings sub-tabs]
Overview
Real-time status:
- Conversations today — cumulative message count
- Scheduled runs completed — tasks finished today
- Average response time — across the last 100 messages
- Token usage — cumulative tokens consumed today
Plus quick actions:
- Hermes UI — open the chat window
- Restart — cycle the container
- View Logs — recent logs
Activity
A timeline showing:
- Every conversation (message + response)
- Scheduled runs (success / failure)
- Code-execution records (Python, JS, Shell)
- System events (container start / stop, upgrade)
Filter by type: All / Conversations / Scheduled / System.
Usage
- 7-day cost line chart
- Token bar chart (by time, by model, by purpose)
- Monthly totals
- Distribution chart (switch between by-model and by-purpose)
Hermes’s Usage view has one extra column versus OpenClaw: code execution count (since Hermes ships a native code sandbox).
Settings
Hermes-specific settings:
| Setting | Description |
|---|---|
| Model Selection | Switch between OpenAI, Anthropic, Google, Groq, and other providers |
| Credential Pool | Rotate multiple API keys to avoid provider rate limits |
| MCP Servers | Connect external MCP tools (key feature) |
| Profiles | Enable multiple isolated instances on one Vi container |
| Version Upgrade | Check for new Hermes releases, upgrade, roll back |
| Messaging Platforms | Connect Signal, DingTalk, Matrix, and other Hermes-native channels |
Differences From Rose / Ada Dashboards
| Item | Rose / Ada (OpenClaw) | Vi (Hermes) |
|---|---|---|
| Code execution log | None | ✓ Shown per run on Activity |
| MCP configuration | Indirect via Tool | Native Settings page |
| Profiles | Single instance | Multiple isolated instances |
| Credential pool | One API key | Auto-rotating multi-key |
| Default messaging platforms | Telegram, WhatsApp, LINE, Discord | Signal, DingTalk, Matrix |
Common Actions
Upgrade the Hermes Version
Settings → Version Upgrade → Check for Updates → Pick version → UpgradeUpgrades take about 1 to 2 minutes, during which Vi is offline. If the upgrade fails you can roll back to the previous version.
Before upgrading, check the Hermes release notes for Breaking Changes that could affect your workflow.
Add an MCP Server
Settings → MCP Servers → Add Server → Fill in endpoint URL and tokenOnce added, Vi discovers the tools the server exposes and adds them to the available tool list.
Enable Profiles
By default Vi runs a single instance. To handle several independent contexts in parallel (finance, research, support, etc.), enable Profiles:
Settings → Profiles → Enable → Add Profile (e.g., finance, research)Each profile has its own memory, MCP configuration, and conversation history.
Monitoring Tips
If Vi slows down or stops responding:
- Overview → check average response time — unusual highs suggest a model or network issue
- Activity → look for error messages — commonly API rate limit or timeout
- Usage → check token usage — a sudden spike often indicates an infinite loop
- Restart the container — Overview → Restart
Related Docs
- Vi’s Full Guide — role, capabilities, use cases
- Engine Selection Guide — OpenClaw vs Hermes
- Hermes Release Notes
- Multi-Container Management