System Status
The System Status dashboard monitors the health, resource utilization, and operational state of the local Orbicus engine running on your machine.
The Background Engine
Orbicus executes background indexing, file watching, and task queues via an on-device engine process. The System Status view provides transparency into this local daemon, ensuring you can monitor its footprint and manage its lifecycle without resorting to terminal process management.
Key operational metrics tracked:
- Daemon Status: Indicates whether the background engine is actively running, idle, or offline.
- System Resource Usage: Real-time CPU percentage and resident memory (RAM) consumed by local indexing and active tasks.
- Engine Uptime: Tracks continuous operating duration since the last restart.
- Socket Connectivity: Verifies active IPC socket connections between your user interface (Desktop App, CLI, or Extension) and the background service.
Managing Engine Lifecycle
If an external tool crashes, an MCP connector becomes unresponsive, or you need to clear temporary memory caches, you can manage the engine directly from the interface:
| Control | Action | When to use |
|---|---|---|
| Start Daemon | Spawns the background engine process. | If the service was stopped manually or failed to launch on startup. |
| Restart Daemon | Gracefully terminates and restarts the engine process. | When refreshing external configuration files, reloading MCP servers, or restoring dropped socket connections. |
| Reset Daemon | Flushes temporary in-memory caches, clears active task queues, and re-initializes engine state. | If an autonomous task becomes unresponsive or in-memory state needs a clean slate. |
| Kill Daemon | Immediately terminates all background engine processes and associated child runners. | Emergency shutdown or troubleshooting local port conflicts. |