Obsidian Internal Links

• A file path provided by the user
• The current file being discussed
• A note referenced by name or ID

2. Execute the Link Resolver

Use the scripts/resolve_links.py script to analyze the note and follow its links.

Dependencies: The script requires PyYAML. If using UV: uv pip install PyYAML. Otherwise: pip install PyYAML or pip3 install --break-system-packages PyYAML on systems with externally managed Python.

python scripts/resolve_links.py <file-path> --vault <vault-path> --depth <depth> --pretty

Parameters:

• <file-path> (required): Path to the markdown file to analyze
• --vault (optional): Path to the Obsidian vault (defaults to /Users/tolga/src/tolgaio/brain)
• --depth (optional): Maximum recursion depth for following links (default: 1)
  • 0 = Extract links but don't follow them
  • 1 = Follow direct links and identify their outgoing links
  • 2+ = Follow links recursively to the specified depth
• --pretty (optional): Format JSON output for readability

Example:

# Follow links one level deep from inbox.md
python scripts/resolve_links.py /Users/tolga/src/tolgaio/brain/0_inbox/inbox.md --depth 1 --pretty

# Just extract links without following them
python scripts/resolve_links.py /path/to/note.md --depth 0

3. Interpret the Results

The script returns a JSON structure containing:

{
  "file": "/path/to/source.md",
  "links": [
    {
      "link_text": "digital-garden",
      "display_text": "Digital Garden",
      "resolved": true,
      "target_file": "/path/to/digital-garden.md",
      "content": "# Digital Garden\n\n...",
      "nested_links": [...]  // If depth > 0
    }
  ],
  "broken_links": ["nonexistent-note"]
}

Key fields:

• links: Array of resolved link objects
  • link_text: The target from [[link_text]] or [[link_text|display]]
  • display_text: What's shown to the user (after | or same as link_text)
  • resolved: Whether the link target was found
  • target_file: Absolute path to the linked file (if found)
  • content: Full text content of the linked file
  • nested_links: Recursively resolved links (if depth allows)
• broken_links: Array of link targets that couldn't be resolved

4. Present the Information

Structure the results for the user based on their request:

For link exploration:

• List all linked notes with their titles
• Show the hierarchy if depth > 0
• Highlight any broken links that need attention

For content synthesis:

• Read and summarize the linked notes
• Extract relevant sections
• Connect ideas across multiple notes

For knowledge mapping:

• Describe the relationship structure
• Identify central hub notes
• Show connection patterns

Link Resolution Strategy

The script resolves links using this priority order:

1. Frontmatter ID: Checks if the link target matches any note's id: field in YAML frontmatter
2. Filename: Matches against the filename (without .md extension)
3. Path-based: For links like [[folder/note]], tries path resolution

Example:

---