New-Session 150 Protocol

Primary workflow

1. Read AGENTS.md in the repo root.

1. Read MEMORY.md in the repo root.

- Load Long-Term Memory protocols first. - Check Lessons (Inbox) and Short-Term for active items. - Session State is deprecated; do not use or update it.

1. Read core project context files (if present):

- README.md for project overview and commands.

1. Auto-Detect & Create Session (CRITICAL):

- If the user's intent is a clear NEW task (e.g., "fix bug X", "implement feature Y", "investigate Z"): - IMMEDIATELY generate a descriptive sessionname (e.g., fix-time-picker-bug). - IMMEDIATELY create the file .sessions/SESSION[date]-[name].md. - DO NOT ASK for permission to create the session. Just do it. - Ambiguity Check: Only ask the user "New or Continue?" if the request implies continuity with the immediate prior context (e.g., "continue", "next step") and you are unsure.

1. Initialize the Session Log:

- Insert structure: ## Meta, ## Progress Log, ## Investigations, ## Decisions, ## Next Steps. - Log the initial User Request. - Incremental Nature (CRITICAL): Treat the session file as a growing journal. When adding new progress or investigation findings, use multireplacefile_content to APPEND them to their respective sections. Do not delete or overwrite historical logs within the file.

1. Summarize in 5-8 bullets:

- Most relevant protocols that will affect the upcoming work. - Any active lessons or warnings. - Key project constraints (tests, tools, conventions).

1. present the Plan & Session:

- State "Created session: [session_filename]". - Propose the plan for the task. - Ask for confirmation on the Plan, not the session creation.

Notes

• If any file is missing, state it briefly and proceed with what is available.
• Keep the summary concise; focus on constraints that change behavior.