Two Obsidian features, at different stages
Session-memory export
Export AI coding-session summaries into AgentMemory/. This is the existing, opt-in session-export --obsidian workflow.
Plan and Today projections
Publish a glanceable Today note, active plans, and learning records into Study/. This guide describes the current development build, not the public release.
One source, useful views, explicit notes back
This is deliberately not two-way sync. A projection can always be rebuilt from the StudyLoop plan, so an Obsidian edit cannot silently change what your next study session follows.
Preview first, then publish
These commands are not in StudyLoop 0.1.0
Keep this page for reference, but wait for the 0.2.0 release unless you are intentionally testing the second-brain development branch.
- 1
Check what is configured
Status is read-only. It reports the provider, destination, and whether publishing is available.
- 2
Preview before writing
Use a dry run to see the exact vault-relative files StudyLoop would create.
- 3
Publish the useful subset
The default is Today plus active plans. Draft and finished plans stay out unless you explicitly include them.
- 4
Keep your own notes separate
Write beside a plan in its .notes.md file, then pull those notes only when you want to fold them back into the source plan.
studyloop brain status
studyloop brain enable obsidian --vault ~/Documents/MyVault
studyloop brain publish --today --dry-run
studyloop brain publish
studyloop brain template --installbrain enable preserves the rest of your StudyLoop configuration. A missing vault is refused unless you deliberately add --create.
A small, predictable folder
The default destination is Study/ inside the chosen vault. Today stays short: one next action, a few alternatives, due reviews, and active topics.
MyVault/
└── Study/
├── Today.md
├── Plans/
│ ├── python-decorators.md
│ └── python-decorators.notes.md
└── Learning Records/
└── python-decorators/
└── LR-0001.mdGenerated files identify themselves
StudyLoop only replaces a file carrying its matching studyloop: ownership marker. If a target is unmarked or belongs to another plan, publishing stops rather than overwriting it.
Pull notes; do not synchronise them silently
Put personal observations beside the generated plan using the same plan ID and a .notes.md suffix. The pull command prints that file without changing either it or the source plan.
studyloop brain pull python-decorators
# Then decide what, if anything, belongs in the real plan.
studyloop plan show python-decorators --markdownPlanned as an optional assistant workflow
xTiles is the next provider stage, but it has not started. The plan is to keep credentials out of StudyLoop and use documented prompts and an opt-in assistant skill before considering a programmatic client.