working-memorylisted

Start with what matters. For full startup context, use Context Bundle: it resolves owner identity, the resolved AI Identity, active scope, active rules, Working Memory, and KFS paths. Working Memory is the lighter daily briefing of active focus areas, priorities, and recent knowledge changes. Codex local Memory is a separate, local recall layer. Even when it is enabled, use Nowledge Mem for current cross-tool context, exact prior conversations, sourced decisions, and continuity with other agents. ## Preferred path If this session exposes the Nowledge Mem MCP server and you need the full startup contract, prefer `read_context_bundle`. Otherwise use `read_working_memory` for a lightweight daily briefing, or the CLI Context Bundle fallback: ```bash nmem --json context --source-app codex ``` For only Working Memory: ```bash nmem --json wm read ``` If the runtime already knows the current project or agent lane, add `--space "<space name>"`. Multi-agent orchestrators can set `NMEM_AGENT_ID="<agent-slug>"` before launching Codex so the Context Bundle resolves the right AI Identity. Add `NMEM_SPACE` only when that whole run should override the identity's default space. Use `NMEM_HOST_AGENT_ID` only for advanced external aliases. ## What you'll find - **Identity and scope**: owner identity, AI Identity, active space, and active rules when using Context Bundle - **Focus areas**: what you're actively working on, ranked by recent activity - **Priorities**: items flagged as impo