Link your project folders to Claude context

Use an ID-based folder system so Claude can open the right index note and resume work from the correct project history.

Done with Claude CodeClaude· Intermediate· Nov 2026

What they did
The author organized their work into Johnny.Decimal-style IDs across life and business, with each ID tied to an Obsidian index note, Markdown files, and a matching disk folder. They then added a small CLI plus agent skills to connect those pieces. When they run jd with an ID or title search, it starts Claude in the right folder so it can read the index note and use its own stored memory and transcripts.
How it went
That lets Claude pull up the human-readable notes and continue earlier conversations with --resume for that specific project. The author says the problem is solved. No usage metrics were reported.
Tips
A setup like this can be built in about half an hour, and the basic version is free. If you want extra convenience from an MCP server, note that it costs money; the ID scheme itself is optional.

Try it yourself with Claude Code

I keep project notes in an Obsidian vault at [vault path], with one index note per [client/project]. Help me build a small CLI or script plus an agent skill so that when I open you from a folder named with an ID like [project ID], you locate the matching index note, read it, and tell me where things stood last time, including decisions, open questions, and next steps. Before you create or edit any files, show me the plan and wait for my approval. Do not change any existing notes unless I explicitly ask you to, and stop before anything that would delete, submit, send, or pay for anything until I confirm.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.