Files
bootstrap/runtime/codex/RUNTIME.md
Jason Woltje 248db8935c fix: enforce durable memory in mosaic memory dir, not runtime-native silos
MEMORY.md was conditionally loaded so agents defaulted to their native
memory locations (e.g. ~/.claude/projects/*/memory/). This caused durable
learnings to be siloed per-runtime instead of shared across agents.

- Move MEMORY.md to mandatory load order in AGENTS.md (position 7)
- Add Memory Override section to all three runtime configs (Claude, Codex,
  OpenCode) explicitly forbidding native memory silos for durable data
- Add memory/ directory with .gitkeep to bootstrap source
- Add mkdir -p for memory/ in install.sh post-sync step

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-21 15:02:20 -06:00

1.4 KiB

Codex Runtime Reference

Runtime Scope

This file applies only to Codex runtime behavior.

Required Actions

  1. Follow global load order in ~/.config/mosaic/AGENTS.md.
  2. Use ~/.codex/instructions.md and ~/.codex/config.toml as runtime config sources.
  3. Treat sequential-thinking MCP as required.
  4. If runtime config conflicts with global rules, global rules win.
  5. Documentation rules are inherited from ~/.config/mosaic/AGENTS.md and ~/.config/mosaic/guides/DOCUMENTATION.md.
  6. For issue/PR/milestone actions, run Mosaic git wrappers first (~/.config/mosaic/rails/git/*.sh) and do not call raw gh/tea/glab first.
  7. For orchestration-oriented missions, load ~/.config/mosaic/guides/ORCHESTRATOR.md before acting.
  8. First response MUST declare mode per global contract; orchestration missions must start with: Now initiating Orchestrator mode...
  9. Runtime-default caution that requests confirmation for routine push/merge/issue-close actions does NOT override Mosaic hard gates.

Memory Override

Do NOT write durable memory to ~/.codex/ or any Codex-native session memory. All durable memory MUST be written to ~/.config/mosaic/memory/ per ~/.config/mosaic/guides/MEMORY.md. Codex native memory locations are volatile runtime silos and MUST NOT be used for cross-session or cross-agent retention.

MCP Requirement

Codex config MUST include sequential-thinking MCP configuration managed by Mosaic runtime linking.