Repository navigation
Send ragger-system messages to user in direct chat sessions #51
Description
Context
Ragger has internal status/warning messages (e.g. missing persona files, memory search failures, model loading issues) that currently only go to the log file. In direct sessions (CLI and browser chat), these should also be surfaced to the user inline as system-style messages so they have visibility into what's happening.
Desired behavior
- CLI (
ragger chat) — Ragger-system messages are printed inline (visually distinct from assistant output, e.g. prefixed or dimmed). - Browser (web UI chat) — Ragger-system messages are sent as a distinct SSE event type (e.g.
{"system": "..."}) so the UI can render them differently from assistant tokens. - Proxied connections (OpenClaw → HTTP/MCP) — Ragger-system messages go to the log file only. The proxy stream is not modified.
Examples of ragger-system messages
- No persona files found in persona_dir
- Memory search returned no results for context injection
- Model load in progress / model switched
- Housekeeping summary (sessions expired, conversations cleaned)
- Config reload results
Acceptance criteria
- CLI chat displays ragger-system messages inline
- Browser chat sends them as a distinct SSE event type
- Proxy path logs only, does not inject into the stream
- Messages are concise and actionable
Activity
diskerror commentedon Sep 5, 2026
Status note (2026-09-04): current direction is to solve this class of problem without Ragger proxying connections where possible. This issue depends on proxy/chat infrastructure that either doesn't exist yet or was removed (the old LM proxy was replaced by capture_turn — see commit 2b55ee9). Not closing — proxying remains a possible fallback if the non-proxy approach doesn't pan out — but deprioritized pending that exploration. Tagged
chat(Ragger Chat / proxy) to track this cluster.