session-management

You can preserve .NET project context across sessions by writing a handoff file that tracks task status, git changes, and learned rules. This ensures the next session resumes accurately with restored memory and MCP tooling readiness instead of starting from scratch.

A session handoff file is a markdown document that captures DONE, PENDING, and LEARNED items from your work. It maintains continuity by providing a structured state snapshot that the next session reads to restore project context and resume tasks exactly where you left off.

To bootstrap MCP tooling in an unfamiliar .NET repository, detect the correct .slnx or .sln file automatically. Once the solution file is located, MCP tooling activates immediately, enabling code analysis and interaction from the first prompt without manual configuration.

Yes, this session management workflow works with any .NET project containing .sln or .slnx solution files. It requires standard markdown context files for handoff state and memory rules to correctly manage the session lifecycle and preserve project context.

When context files like MEMORY.md are missing, the session workflow applies graceful fallbacks to continue operating. It detects the absence of these files and proceeds with the session bootstrap by relying on available git status and solution detection instead of failing outright.

You capture session learnings by running a session end protocol that reviews accomplishments, checks git status, and extracts corrections into durable memory rules. This updates your MEMORY.md file and evolves heuristics in your instincts file, ensuring accumulated knowledge persists for future work.