agent-context-systemlisted

# Agent Context System ## The Problem Agents start from zero every session. You spend an hour getting your coding agent up to speed on a project, close the session, and start from zero the next day. The agent forgot everything. Every session is a cold start. This isn't a limitation of the model. It's a context delivery problem. The agents have the capacity to remember — they just don't have the right inputs at the right time in the right format. ## The Solution Two markdown files. One committed, one gitignored. The agent reads both at the start of every session and updates the local one at the end. - **`AGENTS.md`** — Your project's source of truth. Committed and shared. Always in the agent's prompt. Under 120 lines. Contains compressed project knowledge: patterns, boundaries, gotchas, commands, architecture. - **`.agents.local.md`** — Your personal scratchpad. Gitignored. Grows over time as the agent logs what it learns each session. Session notes, dead ends, preferences, patterns that haven't been promoted yet. That's it. No plugins, no infrastructure, no background processes. The convention lives inside the files themselves, and the agent follows it. ## How It Works ### 1. Setup Run the init script. It creates `.agents.local.md` from a template, ensures it's gitignored, and wires up your agent tool's config (CLAUDE.md symlink for Claude Code, .cursorrules for Cursor, .windsurfrules for Windsurf, copilot-instructions.md for Copilot). ```bash # If you cloned the