Solomon

Solomon is a knowledge base you actually own. Every note is a plain markdown file, sitting in a folder on your disk — no proprietary database, no lock-in. Open that folder in Solomon and it's a vault. Edit it in Solomon, in Obsidian, in a text editor, from a script — the file is the source of truth, always.

On top of that plain-file foundation, Solomon adds the things a modern knowledge base needs, all opt-in and all inspectable as ordinary files:

• Real-time sync — turn it on per vault and your notes replicate conflict-free across devices, with live cursors when you collaborate.
• Agents — markdown assistants (Agents/*.md) that read and write your vault through a reviewable proposal queue — visibly, never silently.
• Skills — reusable instruction packets (Skills/<id>/SKILL.md) you can attach to any agent.
• Bases — live, spreadsheet-like views over your notes' frontmatter, compiled from a small query DSL.
• Widgets — small sandboxed HTML mini-apps you embed inside a note.
• Publishing — share a note, folder, or whole vault as a web page from Solomon's host, source of truth staying in your vault.
• CLI + MCP — a solomon command-line client and a built-in MCP server, so any agent (including Claude Code) can work your vault the same way you do.

Who this is for

Anyone who wants a durable, local-first place for notes, docs, project tracking, or a research library — and wants agents to help fill it in without ever losing control of what changes. If you've used Obsidian, the file model will feel immediately familiar (Solomon vaults and .base files are interoperable with it).

Where to go

Getting Started — the fastest path from zero to a working vault.

• [[Install and first run]] — get the app running and open your first vault.
• [[Your first note and vault]] — create a note, understand frontmatter, see how a folder becomes a vault.
• [[Core concepts at a glance]] — a one-page tour of every concept below, with links to the deep-dive pages.

Concepts — the mental model behind each feature.

• [[Local-first and CRDT sync]] — what "local-first" actually guarantees, how sync rooms work, what never leaves your machine.
• [[Agents and skills]] — how agents are defined, how skills attach to them, and how the propose/approve loop keeps you in control.
• [[Bases and widgets]] — the base query grammar and how widgets embed in a note.

CLI — the solomon command-line client.

• [[solomon CLI reference]] — the three-transport model, global flags, and all 18 subcommands.
• [[HITL delegations (actions)]] — the solomon actions human-in-the-loop delegation flow behind the Ops Delegation board.

MCP — connecting Claude Code, Claude Desktop, or any MCP client to your vault.

• [[MCP tool surface]] — the local MCP server's 17 tools and the propose-vs-force key model.

Search — inline metadata filters that work the same across desktop, CLI, and MCP.

• [[Metadata filters]] — the path:/tag:/has:/[key:value] grammar, and which surfaces support which operators.

Publishing — sharing notes as web pages.

• [[Publish a folder or vault]] — share a file, folder, or whole vault as a web page.
• [[Reader keys and audiences]] — how restricted publications are gated, granted, and unlocked.
• [[The published API and SDKs]] — the versioned public read API behind every publication.

SDK — building on top of Solomon's vault primitives.

• [[TypeScript SDK quickstart]] — construct the generated client and call site(), note(), search().

Playbooks — end-to-end workflows for common goals.

• [[Query your vault with bases]] — write a .base query to build a live view over your notes' frontmatter.
• [[Triage your inbox with an agent]] — point an agent at your notes to summarize, tag, and categorize them.

A note on accuracy

These docs are grounded in the actual behavior of Solomon — every command and flag here was verified against a running build before being written down. If something here doesn't match what you see in the app, the app is likely ahead of these docs (or you're on an older build).