Bring the useful notes.
Keep their meaning.
Use selected Obsidian notes in a connected Claude conversation without moving your entire vault. Start with one task and include the passages it depends on.
Your next conversationOne small reference. A clear way back.
- Choose the notes needed for one task.
- Include the supporting text behind essential links. Keep its title and review date. [1]
- Save a named reference in Multiplist. Confirm the intended account and realm before saving.
- Connect and authorize Multiplist in Claude, then enable it for that conversation. [4]
- Request original content, inspect the returned passage, and build on what it supports.
- Keep open questions visible. Update the separate reference when your maintained notes change. [1]
This checklist is authored synthesis. The complete public reference appears below; it is the evidence, not a claim that Claude executed the task.
The detail that often gets lost
[[Portable handoff#Minimum record]] names a linked note and heading. It does not carry that note's body into another tool. Include the needed passage yourself. [2]
Obsidian keeps notes as local Markdown files. Your maintained originals can stay there while you deliberately save a selected reference elsewhere. [3]
Ask for the saved original
Retrieve the original content of "Selected notes - carry context forward" from Multiplist. Identify its review date. Create a short checklist from these notes, cite the supporting passage, and keep unresolved questions visible. Flag missing linked material or outdated information.
This is a request to try in your own connected Claude conversation. Plan, workspace controls and permissions affect access. The Free plan is limited to one custom connector; setup is not automatic vault synchronization. [4]
Verified in this productionA real saved source, read back exactly
We imported the included public Markdown reference in Multiplist, then retrieved its original content through the connected get_source tool here. All 1,562 characters matched, including whitespace.
Saved title: Selected notes - carry context forward
Source identifier: 7fc31ec8-51f7-484e-a856-744e0cd3555b
Review date: October 19, 2026.
This verifies this account's save and retrieval. It is not a fresh Claude, Obsidian, Cowork or Code execution test. No extracted seeds were generated. Import setup pictures are labeled replays; saved-source pictures are actual captures.
Included in this file
This guide contains a derived checklist, a retrieval prompt, the complete two-note public reference, its source identifier and short official-documentation excerpts. The kit also contains the three Markdown files and a plain-text prompt.
No private conversations, account details, real local filesystem paths, embeddings, credentials or full upstream documentation are included. The relative filenames inside the example are public labels. Review your own verbatim text for personal context before sharing. Multiplist is a hosted service; read its privacy policy before saving sensitive material.
Inspectable evidence
Evidence 1 • complete public source snapshotSelected notes - carry context forward
Imported and retrieved October 19, 2026. Original content; no seed extraction. The supporting passage starts at character 963 and ends before character 1122 (zero-based Unicode code points computed for this guide, not a stored seed locator).
Keep the research question, relevant evidence, source label, review date, and unresolved questions together. Read the supporting passage before building on it.
# Selected notes - carry context forward
Reviewed: 2026-10-19
Scope: Two short public demonstration notes. No private vault content. Local labels below are sample relative filenames. This is a selected reference, not a live mirror.
## From: Carry context forward.md
## The question
How can I use my existing notes in another AI conversation without uploading everything?
## Working decision
Keep the maintained original in the note folder. Share only the passages needed for the next task.
## Essential link
See [[Portable handoff#Minimum record]] before preparing the reference. The link names a note; it does not include that note's text.
## Next task
Create a short checklist for carrying these notes into a connected Claude conversation. Keep the review date and unresolved questions visible.
## Open question
Has the selected reference been updated since the maintained notes changed? Check before reuse.
## From: Portable handoff.md / Minimum record
Keep the research question, relevant evidence, source label, review date, and unresolved questions together. Read the supporting passage before building on it.
## Version boundary
A saved reference is a dated copy. Editing the local note does not update that copy automatically.
## Public references
- Obsidian stores Markdown files in a local vault: https://help.obsidian.md/Files+and+folders/How+Obsidian+stores+data
- Internal links point to files, headings, or blocks: https://help.obsidian.md/links
- Multiplist workflow guide: https://multiplist.ai/learn/how-to-use-obsidian-notes-in-claude
SHA-256 of the exact UTF-8 Markdown bytes: d520a7b48f631abf2432749e706929dc4571e56495d42cc095a81451d0024992
A file checksum detects changes to this snapshot. It does not verify authorship, factual accuracy or future currency.
Return to linked-passage step ↑ · Return to version step ↑
Evidence 2 • official documentationObsidian internal links
Links can point to files, headings and blocks. Obsidian-specific block references are not standard Markdown.
“Block references are specific to Obsidian and not part of the standard Markdown format.”
Read current official documentation (online). Checked October 19, 2026.
Return to the link explanation ↑
Evidence 4 • official documentationClaude custom connectors
Custom connectors require setup, authentication and enablement. Organization controls can apply. The guide identifies per-conversation enablement and the Free-plan limit.
“Free users are limited to one custom connector.”
Read current official documentation (online). Checked October 19, 2026.
Return to the checklist ↑