chats-share

Clawpage

Type /clawpage in any Openclaw chat - conversation becomes a polished archive page at your own URL. 🚀 Deploys to GitHub Pages, Vercel, Netlify, or Cloudflare Pages.

Español · Français · 中文 · 日本語 · 한국어

✨ No manual exports, no copy-pasting, sensitive data auto-redacted

🤔 Why?

AI chats are valuable, but they disappear. Clawpage turns them into publishable content you can save and share.

🚀 Live Demo

Or see a site we use it ourselves: vibe.yelo.cc

📌 Features

• ⚡ Based on Skills — type /clawpage in any chat to start sharing
• 🕐 Any session — not just the current chat, but also any historical session by ID or keyword
• 🚀 No server to manage — pure static, deploys to GitHub Pages, Vercel, Netlify, or Cloudflare Pages for free
• 🔀 Review before you publish — each export opens a PR so you can review content before merging
• 🔒 Share privately — direct link works, but chats stay off the public index by default
• 🛡️ Safe to share — AI-assisted redaction replaces sensitive data with [REDACTED] before export
• 🧠 Full fidelity — tool calls and thinking traces are preserved in the timeline, not stripped out

⚡ Quick Start

Copy and Paste into your agent chat:

Read https://clawhub.ai/imyelo/clawpage and install the clawpage skill,
then run first-time setup for me.

🤖 What the Agent Does During Setup

The agent will scaffold a private GitHub repo, configure clawpage.toml with your Pages URL, push the initial commit, enable GitHub Actions as the Pages source, and register the project so /clawpage works immediately. For the full step-by-step, see skills/clawpage/references/setup.md.

📤 Share a Chat

Once setup is complete, use the /clawpage skill command in any Openclaw chat to export it:

/clawpage

The agent will:

1. 🔍 Locate the session to export — defaults to the current chat; you can also pick any previous session by ID or keyword
2. ✅ Ask you to confirm the title, description, and visibility (public / private)
3. 🔒 Redact any sensitive data you flag
4. 📝 Write the YAML file to your working repo on a new branch (chat/{YYYYMMDD}-{slug})
5. 🔀 Prompt you to open a Pull Request — merging to main triggers the GitHub Pages build

After the PR merges, your chat is live at https://your-domain/chats/{slug}.

⚠️ Before merging: AI-powered redaction is not 100% reliable. Always open the generated YAML in the PR and manually replace any missed sensitive content with [REDACTED]. See How to protect sensitive info for details.

💡 Tip: Set visibility: private (the default) to keep a chat accessible via direct link only, without it appearing on the public index page.

⚙️ How It Works

/clawpage
    │
    ▼
🤖 OpenClaw Skill
    │  1. 🔍 Locate session (current or any historical) → confirm
    │  2. 💬 Extract message history
    │  3. 📝 Populate metadata (title, participants, description)
    │  4. 🔒 Redact sensitive data
    │  5. 📄 Write YAML to your data repo
    │  6. 🔀 Push to new branch → create PR
    ▼
🚀 GitHub Pages
    └── https://your-domain/chats/{slug}

🌿 Branch-Based Workflow

Chats are pushed to a new branch (chat/{slug}) instead of main, with guidance to create a PR for review before merging.

🏗️ Repository Architecture

This repo is a public template. Your actual chat data lives in a separate private working repo — this keeps the template clean and forkable without data contamination.

⚡ Configuration

The web package is configured via clawpage.toml in your working repo root.

Example clawpage.toml (GitHub Pages project site):

site = "https://your-username.github.io"
base = "/your-repo-name"

[template.options]
title = "clawpage"
subtitle = "// conversation archive"
footer = "powered by [@imyelo](https://github.com/imyelo)"

[template.options.promo]
enabled = true

When deploying to Netlify, Vercel, Cloudflare Pages, or a custom domain, set site to your full URL and omit base.

🚢 Deployment

The scaffold includes configuration files for

• ✅ GitHub Pages
• ✅ Netlify
• ✅ Vercel
• ✅ Cloudflare Pages.

For step-by-step instructions, custom domain setup, and free tier limits for each platform, see docs/guide/en/deployment.md.

📋 Data Format

Chat files are stored as YAML under chats/ in your working repo. Generated by the CLI from Openclaw session JSONL files ({id}.jsonl).

File naming: YYYYMMDD-{slug}.yaml

Top-level metadata fields:

Visibility:

• public — appears on the homepage index
• private (default) — accessible via direct URL only, hidden from the index

The timeline: key holds an ordered list of message and event objects. See docs/clawpage-data-format.md for the full schema.

Example file:

title: Debugging Async Issue
date: 2026-02-15
sessionId: cf1f8dbe-2a12-47cf-8221-9fcbf0c47466
model: MiniMax-M2.5
totalMessages: 4
totalTokens: 12345
visibility: public
defaultShowProcess: false
participants:
  Alice:
    role: human
  Claude:
    role: agent

timeline:
  - type: message
    role: human
    speaker: Alice
    tim