Export your knowledge
Export your own knowledge, or a whole workspace, as one ZIP of Markdown, JSONL and original files with checksums, and download your personal data.
Export is a core feature, not an afterthought: an export is complete or it is not an export. Everything you can read goes in, in open formats, and you do not need a Breno account to read it.
Start an export#
Open Export in the left navigation and choose:
| Option | What it contains | Who can do it |
|---|---|---|
| My knowledge | Items you created. | Anyone who can read them. |
| Export everything | Everything you can read in the workspace. | Owners and Admins. A member asking for a whole-workspace export is refused. |
The export runs as a background job and appears in the jobs list, which updates as it progresses. You can Cancel a running job. When it is ready, choose Download. A finished export stays available for seven days, and each download is recorded in the audit log.
Limits keep exports fair: up to three jobs running at once and ten a day.
What you get#
One ZIP named breno-export-<workspace>-<date>.zip, containing:
bundle.json: the manifest, with every item's metadata, provenance and versions.markdown/: the full text of every item (and every earlier version), as Markdown with front matter.files/: your original uploads, byte for byte.memory/,decisions/andgraph/: JSON Lines files, always present even when empty.checksums.sha256: a SHA-256 for every other file.
The format is documented member by member in Export format.
What is left out#
An export contains exactly what you may read, using the same rule as search. An item in a space you are not in, a confidential item beyond your clearance, and another member's Only me item are not in it.
Verify it#
unzip breno-export-*.zip -d export && cd export && sha256sum -c checksums.sha256Download your personal data#
Download my data (any member) builds a personal export that adds account.json next to your knowledge: your profile, sign-in events, sessions and notifications. It is yours alone and is never part of a workspace export.
From other tools#
The REST API (POST /knowledge/export and /knowledge/export/zip) and the MCP tool export_knowledge use the same collector and writer, so the formats cannot differ. Small sets come back inline; larger ones become a job you poll. See Export.
Bring it back#
An export can be imported into another workspace, and the round trip is tested. See Import knowledge.