I use Obsidian daily as a journal system, a knowledge base, and writing tool. But also as a record of what AI coding agents are doing. I don’t always offload work to AI, but when I do, I prefer accountability. So here’s my setup:
- Keep a reliable folder hierarchy in Obsidian for projects. I have
/Project Notes/<ProjectName>as my scheme. - Within it, have an
AI Notesfolder. - Add the following to
AGENTS.mdorCLAUDE.md:
* Keep a record of any approved plans in the form of ``YYYYMMDD-HHMM - Summary.md``
under an `AI Plans` directory under the relevant project directory in
`/Users/chipx86/Documents/Obsidian/Main/Project Notes`. Search for the project
name under here (it may be nested) and, if not found, suggest a name relative
to this and let me correct you if needed. You may create directories within here.
* If there's any particularly interesting tips or concepts that are discovered
during development, record them. If this is specific to a project, file it in a
`Project Tips` directory under the corresponding `Project Notes` directory. If
instead it's more general to programming (not-project-specific), write them to
`/Users/chipx86/Documents/Obsidian/Main/Today I Learned/AI Drafts` (named in
`YYYYMMDD - Summary.md` format). Not every change warrants this, only if it's
noteworthy. You may ask me if there's any doubt.
* For any records living in Obsidian, use Obsidian Frontmatter to specify the
date and tags at the top of the file:
```markdown
---
date: YYYY-MM-DD
tags:
- "..."
- "..."
---
```
Fill out as appropriate. For plans, use the `AIPlan` tag. For interesting notes,
use the `til` tag.(Claude Code usually respects this. Though sometimes I do have to give it a nudge. Always check!)
Keep in mind, coding agents do their job and then forget. And we can easily forget along with them. They don’t think about their work after the fact and they don’t take showers. So keeping records and receipts of their work can be incredibly helpful when going back to a change and wondering, “what the hell was it thinking?”