Vitreus · In development

Your work, in plain
Markdown, kept current.

An AI-assisted Obsidian vault for tasks, project tracking, and journaling. Point it at the tools you already use and it keeps a running picture of your work — synced tasks, weekly plans, weekly reviews, and a knowledge base that gets health-checked instead of quietly rotting.

ObsidianClaude CodeOpenCodeLocal-firstMarkdown

Every tool that promises to organise your work wants to become the place your work lives. Vitreus does the opposite. It is a vault skeleton plus a set of skills and agents for Claude Code or OpenCode — your files, your folder, your API keys, running locally through a harness you already control.

Nothing is hosted by us. There is no account, no server holding your journal, and no migration to do if you decide to stop using it — you are left with a directory of Markdown, which is what you had underneath all along.

Six skills

/vitreus-init, /setup-ai, /generate-report, /obsidian-plugin, /weekly-plan, /weekly-review.

Five agents

vault-curator, concierge, reporter, shrink, obsidianist — each with a job and a lane.

A provider CLI

Reference syncs for Linear, Singularity, and Locu, plus a template for adding whatever you use instead.

A clean vault

Four directories — knowledge, journal, reports, sessions — with neutral templates and sensible plugin defaults.

Four god files

AGENTS.md, TOOLS.md, SOUL.md, MEMORY.md — maintained by the agents, readable by you.

Each tool you connect uses one of three routes, recorded in .vitreus/config.json. Which one depends on what the tool offers, not on what we would prefer.

mcp

The AI harness talks to the tool's MCP server directly. No token stored in the vault at all.

rest

A small script pulls from the tool's API. The token lives in scripts/.env, on your machine.

export

You drop a CSV or JSON export into imports/ and the setup flow turns it into notes.

Setup is three commands, run once. After that the vault only asks for twenty minutes a week, at both ends of it.

Terminal
/vitreus-init      # interview: your tools, your keys
/setup-ai          # connect MCP servers, build syncs, import exports
/generate-report   # baseline vault health check

/weekly-plan       # Monday — pending work into a realistic schedule
/weekly-review     # Friday — what shipped, what stalled, what carries over

Vitreus is in daily use here and not yet released. It will be a paid product — one purchase, one person, and your vault content and API keys stay yours. The repository is private until launch.

Requirements are modest: Obsidian, Node 20 and pnpm, and an AI harness — Claude Code, OpenCode, or Antigravity.