Problem
When the user closes the Agent UI window, the agent stops. There is no way to run GAIA as a background service that persists across sessions. This fundamentally prevents always-on agent operation — the #1 differentiator over cloud chatbots.
Strategic Context
From the OpenClaw strategy (Track B Core Platform):
"Heartbeat (periodic awareness), scheduler (cron-style recurring tasks), event hooks (file system triggers, network events). Runs as background system service. This is the capability that makes an agent, not a chatbot."
"Desktop agent UI: System tray application with status indicator, quick actions, activity log, and settings. Not a full chat interface — a lightweight control panel for a background service."
The system tray is the surface; the background service is the engine. Without this, the autonomy engine (#634) has nowhere to run.
Proposed Components
- Windows service / daemon — Agent process runs independently of any UI window
- System tray icon — Status indicator (idle/working/error), quick actions (pause, open UI, settings)
- Activity log — See what the agent did while you were away
- Auto-start on boot — Optional, configurable
- Graceful shutdown — Clean state persistence on system shutdown
Dependencies
Related
Acceptance Criteria
Problem
When the user closes the Agent UI window, the agent stops. There is no way to run GAIA as a background service that persists across sessions. This fundamentally prevents always-on agent operation — the #1 differentiator over cloud chatbots.
Strategic Context
From the OpenClaw strategy (Track B Core Platform):
The system tray is the surface; the background service is the engine. Without this, the autonomy engine (#634) has nowhere to run.
Proposed Components
Dependencies
Related
Acceptance Criteria