flatbread

Flatbread turns files in Git into a typed relational graph. Files are the records. refs in flatbread.config.js link them. You read the graph through GraphQL, generated TypeScript, or the flatbread CLI.

People use it two ways.

Durable memory for coding agents. The Proof stores an agent's reasoning as markdown records in the repository: Efforts, Issues, Findings, Decisions, Constraints, Risks, Citations, and Blobs. An agent writes them with flatbread proof write and reads them back through bounded queries such as flatbread proof list and flatbread proof blocking-decisions. Records live under .flatbread-proof/, so you commit, review, diff, and revert them like any other file, and the memory outlives the session that produced it. The bundled Proof skill teaches an agent the commands.

Relational content for sites, docs, and internal tools. Markdown and YAML files become typed collections that link to each other. A post names its authors by id, and Flatbread resolves them. You get versioned, reviewable content and joins over files without a CMS database. Start with the Quickstart.

Both paths run on the same engine. Plugins control how Flatbread reads files and turns them into data.

Who it is for: People building coding agents that need memory they can review in Git, and teams building TypeScript sites, internal tools, and starter projects that want versioned content with links between entries.

What Flatbread does not do: