Repository navigation
chat: inject system prompt for CLI/browser sessions; skip for proxied connections #34
Description
Context
Three entry points to Ragger chat have different system-prompt needs:
- CLI (
ragger chat) — Ragger owns the conversation. Should build and inject a system prompt automatically (persona files + memory context + base instructions). - Browser (web UI chat) — Same as CLI: Ragger-owned session, needs auto-injected system prompt.
- Proxied connections (OpenClaw → HTTP/MCP) — Client owns the conversation and sends its own system prompt. Ragger should not inject one.
Current state
ragger chat loads workspace files (SOUL.md, USER.md, etc.) into messages_[0] as a system message via load_workspace_files(). There is no separate base system prompt — the persona files carry all framing.
The proxy path passes requests through unchanged (correct behavior, no action needed there).
Desired behavior
- Add a configurable base system prompt for CLI/browser sessions — likely a
SYSTEM.mdfile in~/.ragger/or a[chat] system_promptkey insettings.ini. - This prompt is injected without tool/skill descriptions — the model should rely on memories already in context, not hallucinate tool calls.
- Proxy path remains untouched: client is responsible for its own system prompt.
Relationship to fading memory
The system prompt is part of the payload composition story. The PayloadBuilder / router model design should account for which prompt components (persona, memory, system framing) are included depending on session origin.
Acceptance criteria
- CLI
ragger chatsessions receive an auto-built system prompt (persona + base framing) - Browser chat sessions receive the same
- Proxied HTTP/MCP requests pass through with no system prompt injected by Ragger
- System prompt contains no tool/skill descriptions
- Configurable: daemon owner can customize the base framing
Activity
Add persona_dir and proxy_system_prompt config (issue #34)
diskerror commentedon Jun 3, 2026
Using hooks from those agents that have them to initiate automatic turn store and summarization.
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.