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

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

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

• ⚡ 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

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.

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.

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.

/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}

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

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.

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.

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.

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
    timestamp: "2026-02-15T06:13:50.514Z"
    content: |
      Message content...

  - type: message
    role: agent
    speaker: Claude
    timestamp: "2026-02-15T06:14:05.123Z"
    model: claude-sonnet-4-6
    content: |
      Response content...

Parses OpenClaw sessions/{uuid}.jsonl raw JSONL files and generates YAML output.

npx clawpage parse <sessions/{uuid}.jsonl> [-o output.yaml]

Astro-based static site generator. Renders chat YAML files into shareable pages.

npx clawpage-web dev     # local dev server
npx clawpage-web build   # build static site
npx clawpage-web preview # preview built site locally

Scaffolding tool to initialize a new working repo from this template.

The generated project includes deployment configuration for GitHub Pages, Netlify, Vercel, and Cloudflare Pages — pick whichever platform you use.

npx create-clawpage <project-name>

# Install dependencies
bun install

# Start demo dev server
bun run dev

# Build demo static site
bun run build

# Deploy demo to GitHub Pages
bun run deploy

This project uses changesets for versioning and changelog management.

# Create a new changeset
bun run changeset

# Check changeset status
bunx changeset status

# Preview version bumps (dry run)
bunx changeset version --dry-run

# Apply version bumps and update changelogs
bun run version

1. Create a changeset before merging a PR: bun run changeset
2. Select affected packages and bump type (patch/minor/major)
3. Write a description of the changes
4. Commit the changeset file with your PR
5. After merging, the changesets action creates a "Version Packages" PR
6. Merging the version PR triggers npm publish

packages/
  cli/     - clawpage CLI (session log parser + YAML generator)
  web/     - clawpage-web (Astro static site)
    src/
      components/  - MessageHeader.astro, ChatMessage.astro, CollapsibleMessage.tsx, Footer.astro, MemoryBackground.astro
      lib/         - chats.ts, config.ts, config-schema.ts
      pages/       - index.astro, chats/[slug].astro
  create/  - create-clawpage scaffolding tool
chats/     - Demo YAML chat files
docs/      - Project documentation
skills/    - OpenClaw Skill definitions

Sites built with this tool:

• Yelo
• Your site here — Add yours by submitting a PR

• See docs/guide/en/deployment.md for deployment instructions, custom domain setup, and platform free tier limits.
• See docs/clawpage-data-format.md for complete frontmatter fields and content format.

Apache-2.0 © yelo, 2026 - present