Skip to content

Sessions cold-spawned by inbound messages get no saved-state injection and never call load_my_context #990

Description

@olegbrok

Field evidence (geordi@pi, 2026-08-03, transcript-verified): a session spawned cold at 12:17 by an inbound Slack DM received NO saved-state injection in its boot prompt and never called load_my_context — it operated all afternoon with no continuity from the morning's saves. (In this incident the save chain had independently already lost the relevant state 2h earlier — see the rewrite-not-merge issue — but this gap is independent: even a perfect save chain would not have reached this session.)

Contrast: wake-path boots (context_restart, scheduler wakes) DO inject saved state prominently. The inbound-message spawn path is the outlier — precisely the path most likely to field questions that need continuity (a human asking about ongoing work).

Fix directions: inject the latest saved context into the boot prompt on ALL session-spawn paths, not just wake-path; or at minimum a boot-prompt directive to call load_my_context before answering anything substantive.

Family: #984 state-continuity.

🤖 Filed by Barsik (evidence: geordi's load-vs-read forensic, 2026-08-03)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions