You can supply a permitted file inventory and excerpts in a regular conversation. This method does not require a vault plugin or establish that ChatGPT can browse your local files.
Supply file paths and real headings
This original fictional vault contains:
Lab/Setup.md
## Safety check
Studio/Setup.md
## Lighting
Projects/Launch.md
## Preparation
The Launch note should send lab staff to the safety check in Lab/Setup.md. It should also offer the Studio setup note for lighting preparation. The word Setup alone does not express which of these two files the author intends.
Use these explicit wikilinks in the Launch note:
Before entering the lab, complete the
[[Lab/Setup#Safety check|lab safety check]].
For the recording session, read [[Studio/Setup|studio setup]].
The text after the pipe is the displayed label. Lab/Setup is the target path, and Safety check is the target heading. Changing the label does not rename the file or create that heading.
Obsidian's internal-link documentation, checked October 24, 2026, describes folder-qualified links and aliases. Vault paths use forward slashes even on Windows. Keep file names and actual heading text in the request instead of asking the model to guess a naming convention.
Request a small link patch
Suggest internal-link changes for one Obsidian note.
Current note path and full text: [PASTE]
Exact permitted vault file inventory: [PASTE]
Relevant existing heading text in each destination: [PASTE]
Intended references and what each should point to: [ENTER]
Link style: Obsidian wikilinks with explicit folder paths.
Return only the changed passages plus a link-target table containing
source note, target path, heading if any, and display label. Use only
listed files and supplied headings. Do not invent notes, headings or
claims about their contents. Flag unresolved references separately.
Do not rename, move, create or publish anything. I will review and
apply the patch in the native vault.
This task follows OpenAI's prompting guidance by naming the source material and desired result. Include only the inventory needed for the passage; unrelated private filenames add no value to the link decision.
Check the target behind the label
Open the proposed lab link in Obsidian. Confirm the actual file path and that the view reaches Safety check. Repeat for the studio link and confirm it opens Studio/Setup.md. Reading the label alone checks the prose, while opening the destination checks the reference.
If a heading was renamed, correct the fragment using the note's current heading. If a proposed destination does not exist, hold the change. A missing-note link can lead to creating a new note; that would conceal an unresolved reference rather than confirm the intended file.
Keep the accepted changes in the native Markdown. Publishing introduces a separate question: whether a website generator includes the files and resolves the vault's link format. The Obsidian static-site guide addresses that output boundary. A link that works inside your vault is the result to confirm here.