Markdown files · visual maps

Markdown files. Visual maps.

Open a Markdown file and see its structure immediately. BloomMD adds a visual layer — local, portable and without a new file format.

Normal Markdown / local files / macOS and Omarchy/Linux

BloomMD Workspace
strategy.mdSource
# Product Strategy
## North Star
- Visual thinking for real files
- No locked workspace format

## Initiatives
### Local-first editor
### Pro workflows
### Optional sync

Text becomes space

Markdown turns into a navigable workspace.

The M1 proof is intentionally concrete: real product recordings, local files and desktop beta builds for macOS and Omarchy/Linux, alongside private web access.

Real recording
Branch moved
Markdown updated

Positioning

Markdown is open and durable. Large documents still become hard to scan.

BloomMD keeps the open file and adds the spatial view that linear text cannot provide.

1

Long documents hide their structure

Headings, decisions and dependencies are in the text, but the spatial model stays invisible.

2

Visual tools create new silos

Most mindmap apps help with thinking, then separate the work from Git, editors and existing Markdown.

3

Knowledge should not depend on a platform

When the format is closed, switching tools becomes a migration project instead of normal work.

New: local OpenClaw agents

Assign a node. Review a proposal. Keep Markdown under your control.

The agent works only on an explicit assignment and only with the selected node's context. It proposes – you decide.

Workflow

From file to working map.

No migration and no new workspace format. Open a file, see its structure and keep using it elsewhere.

Step 1

Open a file

Select or drop a normal .md file.

strategy.md

Use cases

For knowledge that has outgrown a linear list.

strategy.md
# Product Strategy
## Goals
## Initiatives
### Retention
### Launch risk

Connect goals, initiatives and open risks

Use the map to keep strategic work readable while the source stays a plain Markdown document.

Product surface

A workspace for structure, not another drawing canvas.

Visual Markdown maps

Headings become nodes, hierarchy becomes navigable space.

Bidirectional editing

Shape structure visually and edit content without changing formats.

Template library

Start from realistic Markdown examples instead of an empty canvas.

Local-first files

Your work remains portable and compatible with existing workflows.

Backups before writes

BloomMD keeps local safety copies before overwriting files.

Open Knowledge Format

OKF bundles stay deterministic, inspectable and review-first.

Obsidian compatibility

Check Obsidian notes as BloomMD maps.

For M1, real product recordings show local Obsidian notes rendered as BloomMD maps. The full plugin beta distribution follows after this release.

Real recordingLocal Obsidian noteBloomMD map

Desktop beta

Real local work belongs on the computer.

The browser demo is for trying the model. The desktop app opens local Markdown files and folders directly on macOS and Omarchy/Linux in the closed beta.

Your files, your machine

Work directly on a local folder. No upload, no account and no hidden background sync.

External edits show up

Changes from Obsidian, VS Code or Git can be reflected without copying files into a platform.

Open Markdown directly

The beta path includes opening .md files and folders as maps from the native app.

macOS and Omarchy/Linux in the closed beta

macOS arm64 and Omarchy/Linux for x86_64 and aarch64 are available as local beta builds. Windows follows as a separate beta release.

Local-first

Your knowledge should remain yours.

BloomMD starts with files you already control. Sync is optional, not the storage model, and Markdown keeps the escape hatch open.

LLM Wiki / OKF

Agent-maintained knowledge still needs human approval.

BloomMD reads and writes Open Knowledge Format bundles: Markdown pages, source hashes, trust signals and explicit approval before agent proposals are applied.

This works through BloomMD and OpenClaw without Bun, a terminal, or access to a source checkout.

Learn about OKF and LLM Wiki

Technical CLI and MCP tools are optional and intended for teams operating their own LLM Wiki.

Closed beta

Free during beta, intentionally small.

We invite testers in small groups so feedback can be answered. Join the waitlist and we will email you when a seat opens. Demo and templates do not need an invite.

Double opt-in by email. We only write when a beta seat opens - no newsletter. You can unsubscribe from every message.

FAQ

Short answers about files, sync and beta access.

Yes. BloomMD reads and writes open Markdown files. The map is a visual working layer, not a new file format.

Your files are already there. BloomMD makes them visible.

Start with a template or try a real Markdown file in the browser.