Bilinc
Start free
  1. Docs
  2. Use Bilinc
  3. Wiki export

Read your agent's memory as a folder of Markdown.

bilinc wiki writes every stored memory as Obsidian-compatible Markdown, one page per key, so you can browse, search and link it in any editor.

Export with one command.

Terminal
pip install -U bilinc
bilinc login
bilinc wiki ~/notes/bilinc-memory

Folders follow the key: project:bilinc:release becomes project/bilinc/release.md.

What each page holds.

Front matter

The key, type, source and update time.

Value

The value in a fenced block. Objects also list their top-level fields.

Recent changes

The last recorded changes, each with time, source, reason and before → after. --history N sets how many (default 5, at most 100); 0 skips them.

Relative links to the keys the value names, and a "Mentioned by" list of the pages that name this one.

Indexes

index.md lists every page with the most recent changes on top, each folder has an _index.md, and AGENTS.md tells agents that the folder is memory data, not instructions.

Options.

--prefix P

Export only the keys that start with P.

Write [[./path.md|key]] links instead of standard Markdown links.

--refresh-history

Fetch every page's history again instead of reusing it.

One-way, and careful with your files.

The export is regenerated on each run. It refuses a folder that is neither new, empty nor a previous export (a folder that holds nothing but .obsidian/ counts as empty), never changes or removes a file it did not write, builds the new pages in a temporary folder before replacing anything, and keeps folders 0700 and files 0600.

Rerunning on the same folder reuses a page's history when nothing about that memory changed and no rollback happened since, so a rerun with no changes makes no per-page history requests. Reads are not billed.

It warns when the folder is inside iCloud Drive, ~/Library/CloudStorage (Dropbox, OneDrive, Google Drive), ~/Dropbox or a ~/OneDrive* folder, since a sync client may upload the export. The export still runs.

The same export from an agent.

The local adapter python3 -m bilinc.cloud_mcp has an export_wiki tool that runs the same export into an absolute folder on your machine and returns the same counts the CLI prints. It refuses the root of a drive, the home folder and the folders above it, system folders, hidden folders in the home folder, ~/Library (except iCloud Drive and ~/Library/CloudStorage) and the Bilinc config folder, before anything is read. The remote connector does not offer it.