Technical formatting

Preserve code, Markdown, tables, and edit diffs

Developer conversations become difficult to review when formatting collapses. InstaShare keeps code separate from prose and gives file edits a diff-oriented presentation so recipients can understand both the discussion and the concrete change.

Readable technical prose

Headings, emphasis, lists, links, quotes, and tables create structure without requiring the recipient to read raw Markdown.

Code stays code

Inline and fenced code use a monospace treatment with whitespace preserved for commands, snippets, and output.

Edits show before and after

Recognized edit operations use removed and added regions rather than presenting two unlabeled strings.

Formatting designed for engineering artifacts

The renderer supports common Markdown patterns found in agent responses, including fenced blocks, lists, links, headings, and pipe tables. Long code blocks remain scrollable rather than forcing the whole page wider than the viewport.

The goal is faithful, readable structure—not a full arbitrary-HTML Markdown runtime. Raw session text is escaped before formatting so conversation content cannot simply inject page markup.

Edit tools receive a purpose-built view

When an Edit or MultiEdit call includes old and new text, InstaShare renders a compact red/green diff. The full tool input remains available in the details area for cases where the simplified comparison is not sufficient.

This makes a transcript useful beside a code review: the reader can see the intent discussed in prose and the exact replacement the agent attempted in the same timeline.

Copy content without copying the chrome

Message-level copy controls extract the visible text of the turn while omitting interface buttons. Readers can reuse a command, explanation, or code snippet without selecting across neighboring messages.

How it works

01

Escape the source

Text is made safe for HTML output before formatting rules are applied.

02

Recognize block structures

Fences, tables, lists, headings, quotes, and paragraphs are separated.

03

Render technical details

Code preserves spacing, and supported edit inputs become diffs.

04

Adapt to the viewport

Overflow is contained so mobile readers can inspect wide technical content.

Important limits

  • The renderer intentionally implements a practical Markdown subset rather than every extension supported by every Markdown engine.
  • Copied text reflects the rendered turn and may not reproduce the original JSON structure.

Try it in a Claude Code session.

Install the readable skill, then say “share this chat” when the conversation is ready.