Yes. Notes track their code by a content hash, so they follow it when line numbers change or the code moves within a file.
If the content changes enough that the hash no longer matches, the note may become stale, but it's never deleted. You can update or delete it manually.
Yes — notes work with every file type VS Code supports. They're stored separately and never touch your source.
They live in .code-notes/. Commit it to share notes with your team, or add it to .gitignore to keep them local. See Storage format for which sub-paths to ignore.
Commit the .code-notes/ directory. Teammates with the extension installed will see every note.
Yes — through the standalone MCP server. What agents are allowed to do is governed by the trust model: by default (audit) their writes land but are logged and revertible; queue mode holds them for your approval; direct applies them immediately.
In audit mode, open the Agent activity view and click Revert. In queue mode the write never landed — reject the proposal.
No. The workspace is in queue mode and the write became a proposal awaiting your approval. Retrying won't change it — approve or reject it in the Pending agent proposals view.
Notes are plain markdown, readable with any tool. The extension also auto-generates INDEX.json and AGENTS.md in .code-notes/ for machine and agent consumption (Agents & MCP).
Minimal — the extension uses caching and content-hash tracking. Very large files (10,000+ lines) may see slight overhead.
GitHub Issues and Discussions.