mdix 0.1.0

mdix is a command-line toolkit that keeps Markdown knowledge bases consistent, especially when humans and AI agents maintain them together.

mdix - Agent-friendly Markdown Toolkit

mdix is a command-line toolkit that keeps Markdown knowledge bases consistent, especially when humans and AI agents maintain them together.

The setup: You keep a folder of Markdown files — one per entity — with YAML frontmatter for metadata. You browse and edit in Obsidian (or any editor), and an AI agent researches, creates, and curates notes alongside you. Git tracks history. Structure grows organically as you learn more about the subject.

The problem: Over time, this workflow accumulates drift. Filenames follow mixed conventions, frontmatter keys diverge (type vs kind, renamed fields that linger), value vocabularies become inconsistent (active, identified, is_identified), and partial metadata silently propagates into new notes. This makes agent behavior less reliable, search noisier, and automation harder to trust.

What mdix does: It gives the agent that works alongside you a command-line interface to search, validate, and normalize frontmattser across your vault, with dry-run previews, schema contracts, and stable machine-readable output. Tell your agent to run mdix --help and it can orient itself and start using mdix competently.

For more background, see docs/why.md.

Prerequisites

• Python 3.11+
• uv (recommended) or pipx/pip
• jq (optional, used in examples to filter JSON output)

Installation

Recommended: run with uvx (no install)

uvx mdix --help
uvx mdix --root ~/notes find "search term"

Install as a tool

uv tool install mdix
# or
pipx install mdix
# or
pip install --user mdix

Quick start

No git clone needed. Download a demo vault and start exploring:

# Copy a demo vault to your current directory
uvx mdix demo great-discoveries
cd great-discoveries

# Text search across notes
uvx mdix find relativity

# List notes that have a specific frontmatter key
uvx mdix ls --has fm.status

# Query all notes as JSON; filter with jq to show only those with errors
uvx mdix q | jq '[.[] | select((.errors | length) > 0) | {path, errors}]'

There is also an energy storage vault (17 notes with a schema and agent instructions):

uvx mdix demo energy-storage
cd energy-storage

uvx mdix schema validate --human
uvx mdix schema inventory --human

See INSTRUCTIONS.md in that vault for the entry point an agent would use.

Commands

Command	What it does
mdix q	Index all notes as JSON (path, frontmatter, errors). YAML dates are serialized as ISO-8601. Add --fail-on-errors / --strict to exit non-zero on parse errors.
mdix find <text>	Full-text search across notes
mdix ls	List notes, optionally filtered by frontmatter keys (--has fm.status)
mdix fm show <path>	Inspect frontmatter on one note
mdix fm normalize	Batch frontmatter normalization: value remapping, defaults, derived fields, null-key removal. Always supports --dry-run.
mdix schema inventory	Frontmatter key inventory and drift visibility across the vault
mdix schema validate	Check notes against mdix.schema.yml. Exits 2 on violations. Supports --include/--exclude glob filters.
mdix schema migrate	Apply key/value/default/null migrations defined in the schema. Supports --dry-run and --include/--exclude.

Read-only commands (never write files): q, find, ls, fm show, schema inventory, schema validate, and any command with --dry-run.

Commands that write files: fm normalize (without --dry-run), schema migrate (without --dry-run).

Full help:

mdix --help
mdix <command> --help

Schema contract (mdix.schema.yml)

Place an mdix.schema.yml in your vault root (or pass --schema-path):

version: 1
fields:
  title:
    type: string
    required: true
  type:
    type: string
    required: true
    enum: [person, discovery, media, subject]
  position:
    type: string
  kontakt.email:
    type: string
migrations:
  - op: rename
    from: rolle
    to: position
  - op: rename
    from: kontakt_email
    to: kontakt.email
  - op: value_map
    field: status
    map:
      active: identified
  - op: set_default
    field: type
    value: person
  - op: unset_if_null
    field: legacy_note

Then validate and migrate:

mdix --root ~/notes schema validate
mdix --root ~/notes schema migrate --dry-run
mdix --root ~/notes schema migrate

Going further

• docs/workflows.md - Incremental cleanup patterns, scoped migration recipes, CI gates
• docs/why.md - Background on the problem this solves

Status

Early-stage.

License

MIT