✓Direct Answer

Yes. Oyma treats any standard directory of CommonMark files as a native vault. You can open your existing Obsidian folder directly without converting formats, running migration scripts, or breaking your Obsidian workflow.

Zero Migration Required for Obsidian Vaults

If you currently manage knowledge in Obsidian, your notes are stored as plain .md files organized in standard filesystem folders on your Mac. Because Oyma is built on the exact same local-first CommonMark foundation, you do not need to export, convert, or import your data.

You simply select File > Open Vault... (or press ⌘O), point Oyma to your Obsidian vault directory, and begin working immediately.

What Works Out of the Box

Oyma recognizes the core conventions of modern Markdown personal knowledge management:

  • CommonMark & GFM Syntax: All standard headings, bullet lists, bold text, italics, blockquotes, and tables render identically.
  • Wikilinks [[Note Title]]: Bidirectional internal links resolve instantly, allowing you to traverse your knowledge graph without friction.
  • YAML Frontmatter: Document metadata demarcated by triple hyphens (---) is parsed and exposed for sorting, tag indexing, and properties inspection.
  • Nested Folder Hierarchies: Your existing directory tree, subfolders, and category structures are reflected 1:1 in the sidebar.
  • Obsidian Callouts: Standard callout syntax (> [!NOTE], > [!WARNING], > [!TIP]) renders with native styled thematic banners.

Coexisting with Obsidian Concurrently

Because Oyma never writes proprietary database formats to your files, you can use both applications concurrently on the same directory:

~/Documents/KnowledgeVault/
├── .obsidian/               <-- Ignored by Oyma
├── Projects/
│   ├── Q4-Roadmap.md
│   └── Architecture-Review.md
├── Daily Notes/
│   └── 2026-10-09.md
└── Attachments/
    └── whiteboard-diagram.png

Oyma completely ignores the .obsidian configuration folder. Any edits you make in Oyma save directly as standard text on disk, which Obsidian detects instantly through its own file watcher. You can use Oyma for high-speed meeting capture and on-device transcription while keeping your Obsidian plugins and graph view intact.

Shared Attachments and Asset Folders

If your Obsidian vault uses an attachments/ or assets/ subfolder for images and PDFs, Oyma respects that path automatically. When you paste screenshots or embed audio recordings during meetings, Oyma stores the files in your preferred assets directory and generates standard Markdown links readable in both editors.

Why Users Pair Both Tools

Many knowledge workers maintain both applications side-by-side:

  1. Oyma for Real-Time Execution: Lightweight native AppKit performance, zero-latency meeting audio capture via ScreenCaptureKit, on-device Whisper transcription, and daily logs.
  2. Obsidian for Extended Customization: Specialized community plugins, complex Canvas graphs, or Dataview queries.

Both tools read and write the exact same underlying text files with zero lock-in.

Frictionless Dual-Tool Workflows Without Conversion

Because Oyma ignores .obsidian configuration directories and writes pure CommonMark, you can freely alternate between Oyma for meeting capture and Obsidian for graph exploration with zero format conflicts.

You can keep Obsidian open in one monitor to inspect interactive graph views while using Oyma on your laptop screen for high-speed typing and botless call recording, with both apps reading the same files in real time.

Related Questions & Architecture Guides