Export

/xavier export bridges individual notes from Xavier's vault to your personal Obsidian vault. Xavier never writes to your vault without explicit action — export is always file-by-file and always asks before overwriting.

Setup

During /xavier setup, you're asked for your personal Obsidian vault path:

"Where is your personal Obsidian vault? (e.g., ~/vault, ~/Documents/obsidian)"

This is stored as export-vault-path in ~/.xavier/config.md. You can skip it during setup and add it later.

Exporting a note

With a path argument

/xavier export prd/webhook-support

Exports that specific note directly.

Interactive browsing

/xavier export

Xavier shows you a browsable list of exportable notes. Internal directories (personas/, adapters/, loop-state/, review-state/) are excluded. You can export from:

• prd/ — product requirement documents
• tasks/ — implementation task lists
• knowledge/repos/ — architecture maps, decision logs
• knowledge/teams/ — team conventions
• knowledge/reviews/ — review summaries

Where exports land

All exports go to an x-inbox/ subfolder inside your personal vault:

~/your-vault/
└── x-inbox/
    └── x-webhook-support.md

The x- prefix on every file makes Xavier-originated notes instantly distinguishable from your own notes.

Wikilink adaptation

Xavier rewrites internal wikilinks when exporting:

• Links to notes that have been exported → [[x-inbox/x-<filename>]]
• Links to notes that haven't been exported → converted to plain text (no broken links)

This means exported notes work correctly in your vault without dangling references.

Conflict handling

If x-inbox/x-<filename>.md already exists in your vault, Xavier asks before overwriting. No silent overwrites.

You can enable diff display for conflicts by setting export-show-diff: true in your config.

What gets preserved

Exported notes keep their Obsidian-flavored markdown intact:

• YAML frontmatter
• Callouts
• Tags
• Wikilinks (adapted as described above)