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

9
wiki/OpsWardenMemory.md
View File

@@ -19,13 +19,18 @@ ticks, coding agent sessions, and operator CLI use.
| Coding agent | `export WARDEN_AGENT_ID=claude` (or `codex`, `grok`, future ids) |
| Operator CLI | default `warden.operator` when `WARDEN_AGENT_ID` is unset |
## Default Behavior
phase-memory is **on by default** (`WARDEN_MEMORY=1`). Every `warden` command
implicitly loads the canonical store before route/access/worker/sign work. You do
not need a separate activation command for normal use.
## Agent Session Orientation
At the start of a Claude Code, Codex, or Grok session that will call warden:
For Claude Code, Codex, Grok, or future agents, set runtime identity once:
```bash
export WARDEN_AGENT_ID=grok # or claude, codex
warden memory activate --json
```
Then use normal `warden route` / `warden access` commands. Episodes are recorded