webui-export-markdown

Exports chat conversations to Markdown files via POST /api/vibe/export.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/liuyu520/cc-connect-fork --skill webui-export-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webui-export-markdown
Source: https://github.com/liuyu520/cc-connect-fork/tree/main/.claude/skills/webui-export-markdown
Command: npx skills add https://github.com/liuyu520/cc-connect-fork --skill webui-export-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exports chat conversations to Markdown files for offline viewing, archiving, and sharing.

Core Features & Use Cases

  • Two export entry points: Active Tab export collects rich messages including tool usage; History Panel export retrieves session text-only messages for quick sharing.
  • Backend-driven Markdown generation: A POST /api/vibe/export endpoint accepts a structured ExportRequest and returns a downloadable .md file with sanitized filenames and proper content-type.
  • Extensible formatting and localization: The Markdown renders messages by type and supports multiple locales for status messages.
  • Use Case: When reviewing a chat with code/tool interactions, export the session to Markdown to share with teammates or store for compliance.

Quick Start

Use the export feature to download the current chat history as a Markdown file.

Frequently Asked Questions about webui-export-markdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export chat history to Markdown for offline viewing?

You can export chat history to Markdown through two entry points: Active Tab export for rich messages including tool usage, and History Panel export for text-only messages. The feature sends a structured payload to a backend endpoint to generate the downloadable .md file.

Can I export chat conversations with tool interactions from the Active Tab?

Yes, the Active Tab export specifically collects rich messages including tool usage and results. It renders these interactions into a Markdown file, allowing you to share complete chat sessions with tool outputs for team review or compliance.

Do I need a backend endpoint to download chat conversations as a Markdown file?

Yes, this feature requires a backend POST /api/vibe/export endpoint. It accepts a structured ExportRequest payload containing session metadata and messages, then returns a downloadable .md file with sanitized filenames and proper content-type headers.

What is the request size limit to export chat sessions to Markdown?

The request size limit for exporting chat sessions to Markdown is 20MB. The backend POST /api/vibe/export endpoint enforces this limit along with authentication to process the structured ExportRequest payload and return the downloadable file.

Does the Markdown export support multiple locales for status messages?

Yes, the Markdown export supports multiple locales for status messages. The formatting logic renders messages by type and applies localization, ensuring the exported file displays status messages appropriately for different language preferences.

What is the best way to sanitize filenames when downloading chat history as Markdown?

The backend POST /api/vibe/export endpoint applies proper filename sanitization to the returned .md file. This ensures safe and valid filenames for offline storage, preventing invalid characters from causing download issues across different operating systems.