OMP Markdown Export

An OMP extension that exports the current session branch as Markdown.

The extension registers the /export-md slash command and provides three output modes:

• Transcript by default: user and assistant text with clear speaker and message boundaries.
• Annotated with --annotated: the transcript plus a session title, Markdown role headings, icons, and thinking blocks.
• Verbose with --verbose: session metadata, thinking, tool calls, tool results, state changes, and subagent transcripts.

Installation

Install the published package by its npm name:

omp install omp-markdown-export

For local development, install the dependencies:

bun install

Load the local extension for one OMP session:

omp --extension /absolute/path/to/export-markdown

Alternatively, link the local package as a plugin:

omp plugin link /absolute/path/to/export-markdown

Equivalent local-path install:

omp install /absolute/path/to/export-markdown

You can also add the local package path to the extensions list in your OMP configuration. Start a new OMP session after changing the extension source.

At runtime, the extension uses collectSubSessions from the HTML export module when available, and falls back to the session module when the HTML module no longer exports it.

Usage

Export a conversation transcript to the default filename:

/export-md

The default filename is:

omp-session-<session-id>.md

Choose an output path:

/export-md conversation.md

Paths are whitespace-delimited; paths containing spaces are not supported.

Transcript output

/export-md [path]

Transcript mode emits only user and assistant text. Each User: or Assistant: label is enclosed by separator lines so both people and programs can identify message boundaries:

------------
User:

------------

Can you inspect this implementation?

------------
Assistant:

------------

The implementation has two important edge cases.

Include subagent transcripts explicitly:

/export-md --with-subagents conversation.md
/export-md --subs conversation.md

Annotated output

/export-md --annotated [path]

Example:

# Session title

## 👤 User

Can you inspect this implementation?

## 🤖 Assistant

> 🧠 **Thinking**
>
> I should inspect the relevant files first.

The implementation has two important edge cases.

Annotated mode excludes tool calls, tool results, state-change entries, images, and subagent transcripts by default. Add --with-subagents or --subs to include subagent transcripts.

Verbose output

/export-md --verbose diagnostic.md

Verbose mode includes:

• session metadata;
• thinking blocks;
• tool calls and JSON arguments;
• tool results;
• compaction and branch summaries;
• model, thinking-level, and service-tier changes;
• labels and context resets;
• extension messages;
• subagent transcripts.

Inline image payloads are omitted by default because base64 data can make the document very large. Embed them explicitly with:

/export-md --verbose --with-images diagnostic.md

--with-images requires --verbose.

Options

Option	Effect
--annotated	Add the session title, role headings, icons, and thinking blocks.
--verbose	Export the complete diagnostic transcript.
--with-subagents	Include nested subagent transcripts outside verbose mode.
--subs	Alias for --with-subagents.
--with-images	Embed base64 images in verbose output.

--annotated and --verbose are mutually exclusive. Unknown options are rejected instead of being interpreted as output paths.

Privacy

The generated file remains local; this extension does not upload it. Exported content may contain prompts, reasoning, source code, file paths, tool output, credentials, or other sensitive data. Review the file before sharing it.

Development

Run the focused regression tests:

bun test index.test.ts

Check that the extension bundles:

bun build index.ts --outdir /tmp/omp-export-md-check --external '@oh-my-pi/*'