r2mopi-markdownrender

Pi coding agent extension + theme that ports the report rendering style used by the R2MO Codex fork TUI (codex-rs/tui/src/markdown_render.rs, status_indicator_widget.rs) to Pi's interactive transcript.

pi install npm:r2mopi-markdownrender

Then run /reload, select the bundled theme once via /settings → Theme → mxt, and use /mdstyle to switch render styles.

What it does

Status symbols are written at the start of a report line, with or without a list bullet:

✓ build passed
! cache refresh needs a second look
i Windows coverage missing
ℹ informational note
✦ additional remark
- ✓ works inside a bullet too
[i] the letter i is only detected in bracketed form

Commands

Configuration persists in <agent-dir>/r2mopi-markdownrender.json ($PI_CODING_AGENT_DIR or ~/.pi/agent).

Styles

a/b/c come from work/markdown-style-options.html; codex is what actually landed in the fork.

Task markers: why [x]/[ ] and not ☑/☐

The fork hardcodes ☑/☐ (codex-rs/tui/src/markdown_render/task_lists.rs). Those two are a trap in a terminal:

• SF Mono and Andale Mono have no glyph for either character.
• ☑ is Extended_Pictographic, so the missing glyph falls back to Apple Color Emoji and is drawn as a double-width colour emoji.
• Pi and Codex both measure the marker as one cell, so the hanging indent of a task item lands one column short — the checkbox and its text no longer line up.

Task items therefore keep the ASCII markers [x] / [ ]. ASCII always measures and draws as three cells, in every font and every terminal, and it is exactly what Pi's own Markdown renderer emits (pi-tui dist/components/markdown.js). In ANSI mode the marker is coloured — green when checked, grey when not — without changing its width. The rewrite branch stays enabled so a task line never also picks up the 🔸 list icon.

Everything else in the codex style (✨ 📌 🔸) is emoji by design and measures two cells on both sides, so it stays aligned.

List icon: the fork's 🔸

Unordered items render as - 🔸 (SMALL ORANGE DIAMOND, U+1F538), exactly like the fork. The same diamond also exists one size up, 🔶 (LARGE ORANGE DIAMOND, U+1F536): both are East Asian Wide, both measure and draw as two cells, and both come from the same emoji font, so swapping them is purely cosmetic and never moves the indent. 🔹/🔷 are the small/large blue pair. ◆ (U+25C6) is the narrow one-cell alternative, but it comes from the monospace font instead of the emoji font, so it reads as a small diamond again.

Theme

themes/mxt.json is a full 56-token Pi theme (built from the built-in dark theme, so every token is present) with an mxt* variable palette:

• mdHeading green, mdLink blue, mdCode the fork's inline-code blue #63a8f8 (CHATGPT_BLUE_200), mdCodeBlock teal, mdQuote green
• Catppuccin-style syntax* colors
• accent = the fork's plan-heading green #87ff5f (rgb_color((135, 255, 95)), history_cell/plans.rs) so rpiv-todo's heading reads like Updated Plan; accent is shared, so see Plan and todo colours below for what else follows it
• success/error/warning aligned with the ✓ ! ✗ symbol colors
• toolSuccessBg/toolErrorBg (#1e2a22/#3a1c22) tint a settled tool call green or red without recolouring its text — Pi only paints the text of a failed call red in some renderers (edit/write previews, [invalid arg]), so the background is what makes every failure visible
• export backgrounds tuned for HTML export

Because only one mdHeading token exists, the theme alone cannot color heading levels differently — that needs the ANSI layer.

Plan and todo colours

The fork's Updated Plan cell hardcodes exactly one colour and takes the rest from its palette: the heading • 🧬 Updated Plan · n/m complete is rgb_color((135, 255, 95)) — bright green, bold — completed steps are dim plus struck through, in-progress steps use accent_color() (the fork's UI_ACCENT = CHATGPT_BLUE_200, a blue), and pending steps are dim.

Pi's todo list (rpiv-todo) draws itself, so its colours come from theme tokens:

The heading is the one element that gets the fork's bright green, because accent is the token rpiv-todo reads for it (todo-overlay.ts:125). The catch is that Pi has a single accent used as a foreground colour in roughly 176 sites — the read/grep/find path colours, every selector, the loaders, the compaction spinner — so those follow the heading to green, and the spinner no longer keeps the theme's sky blue. The fork separates the two: its accent stays blue and only the plan heading is green. borderAccent and toolTitle keep sky, so composer and tool borders stay blue.

Back to a sky accent (sky heading, green on completed rows only):

// themes/mxt.json
"accent": "mxtSky",

Inline code, commands, paths and links

The fork paints every backticked span one colour: the inline-raw syntax scope, falling back to accent_color() (CHATGPT_BLUE_200 = #63a8f8). It singles out only two things — skill links (mauve, underlined) and bare URLs (web_links.rs, link style) — so a command, a path and a skill name are never told apart. A third case, file citations, only exists for the fork's own codex-file-citation{…} marker protocol.

This package sets the base colour to the fork's #63a8f8 through the mdCode token, so backticked spans look like the fork out of the box, and then lets the ANSI layer read what each span actually holds:

/mdstyle code off disables the layer. Command and path detection is a heuristic on the span text, so a code-looking word can land in the neighbouring colour; the reset button is the theme's mdCode.

The ANSI layer and its limits

Pi renders assistant Markdown itself, so content-level icons are the only thing a theme can never provide. Everything else here is achieved by injecting ANSI escapes into the Markdown source before Pi parses it (via registerMarkdownTransformer). Pi's TUI keeps width math ANSI-aware, so wrapping and padding stay correct — verified against @earendil-works/pi-tui's Markdown component.

Known gaps (honest list):

Use /mdstyle icons if any of that matters; the theme still applies.

Development

# try it without installing
pi -e ./plugins/pi/r2mopi-markdownrender

# check what would be published
npm pack --dry-run

# publish — versions are owned by the family scripts (see ../README.md)
cd ../../plugins/pi && ./npm-login.sh && ./npm-publish.sh --plan

License

MIT