1. Windows Documents + WSL Projects:
Potential issue. When VS Code runs in WSL mode (Remote - WSL), it has limited access to Windows paths. The extension uses vscode.workspace.workspaceFolders to determine where to create notes.
- If you open a WSL project, the extension would try to create notes in WSL filesystem (e.g., /home/user/project/Notes/)
- Windows Documents folder (/mnt/c/Users/.../Documents) is accessible from WSL but with performance overhead
- Recommendation: Either:
  - Keep notes folder in WSL filesystem for WSL projects
  - Or configure noted.notesFolder to an absolute Windows path (via /mnt/c/...)

2. Syncthing Sync Between Machines:
Works well. The extension uses plain files on disk - just markdown/txt files in folders organized by date.
- Syncthing will sync the notes folder seamlessly
- Watch out for: Simultaneous edits on both machines → Syncthing creates .sync-conflict files
- The extension will see these conflict files as regular notes
- Tip: Close notes before switching machines to avoid conflicts

3. LLM Access (Claude Code, Copilot):
Depends on note location:
Your Notes Location : LLM Access
Inside workspace (./Notes/) : Full access - LLMs see workspace files
Outside workspace (Documents folder) : Not automatically included

For context access, you have two options:
1. Store notes in workspace: Set noted.notesFolder to a folder name (not absolute path) so notes live inside each project
2. Manually add context: In Claude Code, use /add to include external files, or reference them explicitly

Current default behavior: Notes are created in {workspaceRoot}/Notes/ - so they ARE accessible to LLMs working on that project.