~/wiki
Récent+ Ajouter

Obsidian Integration

Mis à jour le 2025-01-04Confiance : high
obsidian-integrationllm-wiki-patternknowledge-visualizationgraph-viewmarkdown-editingandrej-karpathywiki-browsingreal-time-collaborationweb-clipperdataview-pluginmarp-integrationattachment-handlinghotkey-workflows

The recommended interface pattern for llm-wiki-pattern implementations where humans browse and explore wiki content in obsidian while LLMs act as programmers making live edits to the underlying markdown files. Creates seamless collaboration between human intuition and LLM maintenance.

Integration Model

Collaborative Workflow:

  • LLM agent open on one side, Obsidian open on the other
  • LLM makes edits based on conversation and source ingestion
  • Human browses results in real time - following links, checking graph view, reading updated pages
  • Metaphor: "Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase"

This creates a natural division of labor where humans excel at exploration and pattern recognition while LLMs handle systematic maintenance and content generation.

Essential Obsidian Features

Graph View:

  • Best way to visualize wiki structure and relationships
  • Identifies hubs (highly connected pages) and orphans (isolated pages)
  • Reveals emerging themes and knowledge clusters
  • Essential for understanding wiki evolution over time

Real-time Markdown Editing:

  • See LLM changes appear instantly in Obsidian
  • Navigate between updated pages immediately
  • Visual feedback on cross-reference creation and updates

Wikilink Support:

  • Native support for internal links between pages
  • Automatic backlinking and reference tracking
  • Foundation for the associative trail navigation

Obsidian Web Clipper:

  • Browser extension that converts web articles to markdown
  • Essential for quickly adding sources to raw collection
  • Preserves formatting and structure for LLM processing

Dataview Plugin:

  • Runs queries over page frontmatter (YAML metadata)
  • Generates dynamic tables and lists from wiki content
  • Useful when LLM adds structured metadata (tags, dates, source counts)

Marp Plugin:

  • Markdown-based slide deck format support
  • Enables generating presentations directly from wiki content
  • LLM can create slide decks as query output format

Attachment Management:

  • Set "Attachment folder path" to fixed directory (e.g., raw/assets/)
  • Bind "Download attachments for current file" to hotkey (e.g., Ctrl+Shift+D)
  • Downloads all images locally for LLM analysis and stable references

Image Handling Workflow

Process:

  1. Clip article with Obsidian Web Clipper
  2. Hit download hotkey to store all images locally
  3. LLM reads text first, then examines referenced images separately
  4. Slightly clunky but works well for multimodal content integration

Benefits:

  • Stable image references (URLs don't break)
  • LLM can analyze images directly
  • Complete offline functionality

Version Control Integration

Since the wiki is just a git repo of markdown files:

  • Full version history of all changes
  • Branch different analysis directions
  • Collaborate with others through standard git workflows
  • Track LLM edits over time for quality assessment

Index-Driven Exploration:

  • Start with index.md for wiki overview
  • Follow category-based organization
  • Jump to specific pages via search or links

Graph-Driven Discovery:

  • Use graph view to find connection patterns
  • Identify knowledge gaps (missing connections)
  • Explore topic clusters and emerging themes

Log-Based Timeline:

  • Review log.md for chronological wiki evolution
  • Understand how knowledge accumulated over time
  • Identify periods of high activity or major updates

Real-time Collaboration Benefits

Immediate Feedback:

  • See LLM understanding reflected in page updates
  • Catch misinterpretations or missed connections quickly
  • Guide LLM emphasis through real-time review

Enhanced Exploration:

  • Follow interesting connections as they're created
  • Discover unexpected relationships through graph visualization
  • Build on LLM insights through guided browsing

Quality Assurance:

  • Verify cross-references are accurate and meaningful
  • Ensure page updates maintain consistency
  • Check that new content integrates well with existing knowledge

Scaling Considerations

As wikis grow beyond ~100 pages:

  • Graph view becomes dense but still valuable for cluster identification
  • Search becomes more important than browsing
  • Consider complementary tools like qmd for advanced search capabilities

The Obsidian interface remains effective even at scale due to its flexible navigation options and powerful visualization capabilities.

See also