coulomb/ops-warden
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enable implicit phase-memory activation on every warden command.

Browse Source 
Load coordination memory by default via ensure_memory_context on app bootstrap
and route/access flows; invalidate cache after episode writes. WARDEN_MEMORY=0
remains the opt-out. Document that warden memory activate is optional only.
This commit is contained in:
Bernd Worsch
2026-07-03 00:49:36 +02:00
parent 04929e7981
commit 120de64bcb
6 changed files with 129 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
AGENTS.md
View File

@@ -161,15 +161,19 @@ get wrong.
ops-warden shares a **phase-memory** store across worker ticks, coding agent
sessions, and operator CLI use.
**At session start** (Claude Code, Codex, Grok, or future agents):
**Default:** phase-memory loads automatically on every `warden` command when
`phase-memory` is available. No separate activation step is required.
**Agent sessions** should set runtime identity once per session:
```bash
export WARDEN_AGENT_ID=grok # or claude, codex
warden memory activate --json
```
**During work:** use normal `warden route` / `warden access` / `warden sign`;
episodes are recorded automatically unless `WARDEN_MEMORY=0`.
Then use normal `warden route` / `warden access` / `warden sign` / `warden worker`.
Episodes are recorded automatically unless `WARDEN_MEMORY=0`.
`warden memory activate` is optional introspection/refresh, not a prerequisite.
**Store:** `~/.local/share/warden/memory/` (override: `WARDEN_MEMORY_STORE`).