Sophie Optimizer

**Judgment:** A focused, pragmatic optimizer for a single OpenClaw "main" session that trades aggressiveness (hard resets) for simplicity and sustained performance. Well-suited to self-hosted or low-stakes environments where occasional disruptive resets are acceptable. **What it does well** - Monitors token usage and only intervenes when a threshold is exceeded (if tokens < ~80k it exits without action). - On trigger, follows a clear protocol: snapshot → distill → reset. - **Snapshot:** saves a JSON summary of the current context to `archives/YYYY-MM-DD_HH-MM.json`. - **Distill:** updates `MEMORY.md`, keeping the top 3 recent summaries and indexing older ones for long-term reference. - **Reset:** runs `reset.sh` to wipe session JSONL files and restart the `openclaw-gateway` service. - Simple operational model: run manually or via cron/heartbeat; minimal moving parts (Python script + shell script + archive directory). **Key risks / caveats** - **Data loss / disruption risk:** Hard resets wipe session JSONL files and restart the gateway. If run too frequently or at the wrong time, it can: - Destroy in-progress conversations or ephemeral state. - Cause brief service downtime or flapping in production. - **Configuration sensitivity:** Paths and assumptions appear tailored to a specific OpenClaw layout (`/home/lucas/openclaw/...`, `main` session, `openclaw-gateway`). Non-matching deployments may require careful adaptation and testing. - **Archival privacy:** JSON snapshots and `MEMORY.md` may contain sensitive user data. They need proper filesystem permissions, rotation, and possibly encryption in real deployments. - **Limited granularity:** The reset mechanism is coarse (wipe & restart) rather than selectively trimming or compressing context, which may be too heavy-handed for multi-tenant or high-availability systems. **Recommended scenarios** - Self-hosted or lab/dev OpenClaw instances where: - There is a single or primary long-lived session that tends to hit token limits. - Occasional short downtime and session resets are acceptable. - The operator wants an automated way to preserve high-level summaries before context is cleared. - Power users running a personal assistant who value a clean, performant context over preserving every conversational detail. **Use with caution** in: - Production, multi-user, or high-availability environments where service restarts and session wipes can disrupt users. - Regulated or sensitive domains unless archival and memory files are handled with strict security and retention policies.