Rose Dashboard (oc-1)
Rose is your primary AI companion, with the highest permission scope and the most complete tool set. System administration, cross-container coordination, host-level work — Rose handles it.
Role Definition
Rose — The All-Around Companion
| Attribute | Value |
|---|---|
| Permission Level | Host root — full access to the host and every container |
| Resource Allocation | High — ample CPU and memory |
| Default Model | High-performance large language model |
| Primary Use | System administration, technical development, complex coordination |
Use Cases
Rose is the right choice for:
- System administration — monitor host resources, manage Docker containers, schedule maintenance
- Cross-container coordination — move data between containers, wire services together
- Host-level changes — Nginx tweaks, SSL certificates, OS tuning
- Technical development — write scripts, build applications, deploy services
- Data processing — log analysis, report generation, transformations
Container Info and Status
The Rose Dashboard surfaces oc-1 container details:
| Field | Description |
|---|---|
| Container ID | Docker container identifier |
| Status | Running / Stopped / Restarting |
| Uptime | Time since the container started |
| Installed Version | Docker image tag currently in use |
Health Checks
The system periodically probes Rose’s health:
- Healthy — running and responsive
- Degraded — responsive but slow
- Unhealthy — broken, may need a restart
Resource Monitoring
Real-time resource usage for Rose’s container.
CPU Usage
The current CPU share the container is using. If sustained over 80%, consider:
- Checking for a long-running large task
- Rescheduling tasks
- Restarting the container if needed
RAM Usage
Memory usage versus limit. Rose is usually provisioned with more memory for complex work.
Disk Usage
Disk usage inside the container:
- Log file size
- Downloaded files and data
- Working directory contents
Gateway Connectivity
The Gateway is the bridge between Rose and the outside world:
- Receives messages from Telegram / WhatsApp / LINE / etc.
- Sends replies back to users
- Maintains WebSocket connections
Status Indicators
| State | Icon | Meaning |
|---|---|---|
| Connected | Gateway is healthy | |
| Connecting | Establishing connection | |
| Disconnected | Connection lost — check network |
Reconnection
If the Gateway shows Disconnected, it retries automatically. You can also:
- Click “Reconnect”
- Restart Rose’s container if it fails repeatedly
- Check the host’s network settings
Agent List
Processes currently running in Rose’s container:
| Agent | Function |
|---|---|
| Main Agent | Core conversation handling |
| Heartbeat | Periodic status reporting |
| Skill Runner | Skill execution engine |
| Channel Handler | Messaging platform integration |
Each agent shows:
- Running state
- Last-active time
- Resource usage summary
Model Configuration
Rose supports multiple model setups.
Primary Model
Used for general conversation and task handling.
Secondary Model
Used for specialized tasks (image analysis, code generation).
Options
- Model selection — switch between available models
- Temperature — controls reply creativity (0–1)
- Max tokens — caps the length of a single reply
Defaults work for most tasks. Raise temperature for more creative replies, lower it for precise technical answers.
Action Buttons
Rose Dashboard offers:
OpenClaw UI
Opens the OpenWebUI dashboard to start chatting with Rose.
This is the main way to interact with Rose. Opens in a new tab.
Terminal
Opens a terminal inside Rose’s container — run commands directly.
# Common commands
ls -la # List the working directory
openclaw status # OpenClaw status
openclaw gateway logs # Gateway logs
ping google.com # Network reachability
Stop / Start
Stop or start Rose’s container.
Stopping Rose interrupts every ongoing conversation and task. Confirm nothing critical is running first.
Logs
View Rose’s container logs for:
- Debugging
- Tracing task execution
- Monitoring activity
Update
Update Rose’s container to the latest version.
Upgrade flow:
- Click “Update”
- The system pulls the newest image
- The container restarts briefly (~30 to 60 seconds)
- Service resumes automatically when the upgrade finishes
Update periodically to stay current on features and security patches. Off-peak hours are the safest window.
Magic Token Copy
The Magic Token is a short-lived credential used for:
- Quick OpenWebUI sign-in
- Pairing mobile devices
- API authentication
How to Copy
- Find “Magic Token” on the Rose Dashboard
- Click “Copy Token”
- The token lands in your clipboard
Magic Tokens are time-limited. Do not share them. If you suspect a leak, restart the container to issue a new one.
Recommendations
- Daily chat — Rose is the best fit for complex questions
- Technical tasks — leverage Rose’s root to run system-level operations
- Cross-container work — Rose coordinates tasks across containers
- Stay up to date — run the latest Rose for best performance