discovery. `SOUL.md`, `IDENTITY.md`, `TOOLS.md`, and `USER.md` are forwarded as

Codex developer instructions. `HEARTBEAT.md` content is not injected; heartbeat

turns get a collaboration-mode note pointing to the file when it exists and is

non-empty. `MEMORY.md` and active `BOOTSTRAP.md` content keep the normal

turn-context role for now.

non-empty. `MEMORY.md` content from the configured agent workspace is not pasted

into every native Codex turn; when memory tools are available for that workspace,

Codex turns get a small workspace-memory note and should use `memory_search` or

`memory_get` when durable memory is relevant. If tools are disabled, memory

search is unavailable, or the active workspace differs from the agent memory

workspace, `MEMORY.md` falls back to the normal bounded turn-context path. Active

`BOOTSTRAP.md` content keeps the normal turn-context role for now.

On non-Codex harnesses, bootstrap files continue to be composed into the

OpenClaw prompt according to their existing gates. `HEARTBEAT.md` is omitted on

normal runs when heartbeats are disabled for the default agent or

`agents.defaults.heartbeat.includeSystemPromptSection` is false. Keep injected

files concise, especially `MEMORY.md`. `MEMORY.md` is intended to stay a curated

long-term summary; detailed daily notes belong in `memory/*.md` where

files concise, especially non-Codex `MEMORY.md`. `MEMORY.md` is intended to stay

a curated long-term summary; detailed daily notes belong in `memory/*.md` where

`memory_search` and `memory_get` can retrieve them on demand. Oversized

`MEMORY.md` files increase prompt usage and can be partially injected because of

the bootstrap file limits below.

non-Codex `MEMORY.md` files increase prompt usage and can be partially injected

because of the bootstrap file limits below.

<Note>

`memory/*.md` daily files are **not** part of the normal bootstrap Project Context. On ordinary turns they are accessed on demand via the `memory_search` and `memory_get` tools, so they do not count against the context window unless the model explicitly reads them. Bare `/new` and `/reset` turns are the exception: the runtime can prepend recent daily memory as a one-shot startup-context block for that first turn.

default: `always`). Detailed raw/injected counts stay in diagnostics such as

`/context`, `/status`, doctor, and logs.

For memory files, truncation is not data loss: the file remains intact on disk,

but the model only sees the shortened injected copy until it reads or searches

memory directly. If `MEMORY.md` is repeatedly truncated, distill it into a

shorter durable summary and move detailed history into `memory/*.md`, or

intentionally raise the bootstrap limits.

For memory files, truncation is not data loss: the file remains intact on disk.

On native Codex, `MEMORY.md` is read on demand through memory tools when

available, with bounded prompt fallback when tools cannot run. On other

harnesses, the model only sees the shortened injected copy until it reads or

searches memory directly. If `MEMORY.md` is repeatedly truncated there, distill

it into a shorter durable summary and move detailed history into `memory/*.md`,

or intentionally raise the bootstrap limits.

Sub-agent sessions only inject `AGENTS.md` and `TOOLS.md` (other bootstrap files

are filtered out to keep the sub-agent context small).