Describe the bug
The rollout (JSONL session file) is writing duplicate base.instruction entries. Each turn or event cycle writes the base instruction to the rollout file again, even though it only needs to appear once (or at most, once per session).
Current behavior
Looking at the rollout files, base.instruction appears multiple times — it seems to be written on every turn initialization rather than once at session creation.
Impact
- Bloated rollout files
- Redundant data that makes replay slower
- Inefficient storage usage
Expected behavior
The base.instruction should be written only once when the session is created, not duplicated on each turn.
Where to look
crates/core/src/conversation/records.rs — rollout record writing- Session initialization flow
- Turn initialization flow
Describe the bug
The rollout (JSONL session file) is writing duplicate
base.instructionentries. Each turn or event cycle writes the base instruction to the rollout file again, even though it only needs to appear once (or at most, once per session).Current behavior
Looking at the rollout files,
base.instructionappears multiple times — it seems to be written on every turn initialization rather than once at session creation.Impact
Expected behavior
The
base.instructionshould be written only once when the session is created, not duplicated on each turn.Where to look
crates/core/src/conversation/records.rs— rollout record writing