self-commenting

Embed grep-searchable AICODE markers (AICODE-NOTE, AICODE-TODO, AICODE-FIX) directly in your code to create persistent cross-session memory. These annotations let you leave explanations of decisions, bugs, and fixes that survive beyond a single conversation, so future sessions can grep and retrieve the context immediately.

Use AICODE-FIX markers to embed structured explanations of the problem, its cause, and the solution directly in the code where the fix occurs. This transforms isolated bug fixes into searchable patterns that future sessions can discover and reuse without losing the original reasoning.

Yes. AICODE markers are designed to be grep-searchable, so you can scan your entire codebase for AICODE-NOTE, AICODE-TODO, or AICODE-FIX entries at any time. This enables fast retrieval of annotations without storing them separately from the code.

Run a grep query across your codebase to find all existing AICODE markers before editing. This workflow step ensures you see prior decisions, known issues, and fixes related to the code you're about to modify, restoring lost context from previous sessions.

AICODE markers stay in place within the code files, so they persist through refactoring as long as the annotated lines remain. If code is removed, markers go with it; moving or copying code preserves markers in their new location, maintaining continuity of documented decisions.

No. AICODE markers are plain-text comments, so they work with any editor, version control system, or CI tool. You only need grep or a text search to retrieve them, making adoption zero-friction in existing workflows.