# Turn a pile of agent pages into one clean bundle

If you use AI agents to publish docs, you eventually end up with a dozen lucid.page links floating around chat history. A bundle ties them together: one URL, a landing page, and your pages as ordered chapters.

Contents

Think of it as the difference between sending someone twelve links and sending them a small book.

# What a bundle actually is

A bundle is a page of its own with:

a landing page (title plus an intro you write in Markdown)
an ordered list of chapters, where each chapter is one of your existing pages
chapter URLs nested under the bundle, like lucid.page/my-guide/getting-started

Readers get previous and next navigation between chapters, and the bundle gets its own share card when it’s public or unlisted.

# The one requirement

Every page in a bundle must be owned by your account. Anonymous pages can’t join a bundle until you claim them, so if your agent has been publishing without a key, open those claim links first (or just read Your agent published a page. Now what? and come back).

# Make one from your agent

With the MCP server connected (Claude Desktop, Cursor, Claude Code, whatever you run):

Create a bundle called “Onboarding Guide” with my pages intro-to-the-stack, deploy-pipeline, and how-we-review-prs, in that order.

The agent calls create_bundle and hands you the bundle URL. Up to 200 chapters, which should cover most onboarding programs and then some.

From curl it looks like this:

curl -X POST https://lucid.page/bundles \
  -H "Authorization: Bearer lp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Onboarding Guide",
    "visibility": "public",
    "markdown": "Everything a new hire needs, in the order they need it.",
    "items": [
      { "doc_slug": "intro-to-the-stack", "nav_title": "The stack" },
      { "doc_slug": "deploy-pipeline", "nav_title": "Deploying" },
      { "doc_slug": "how-we-review-prs", "nav_title": "Code review" }
    ]
  }'

path_slug on an item controls the chapter’s URL segment if you want something prettier than the doc’s slug. nav_title controls what readers see in the chapter list.

# Updating later

Bundles update in place: change the intro, reorder chapters, add new ones, remove dead ones. The chapter pages keep their own URLs and can still be shared on their own. Deleting a bundle doesn’t delete the chapters, it just dissolves the wrapper.

One rule that bites people: a bundle that isn’t private can’t contain private chapters. Keep the visibility of the parts and the whole consistent.

# What people use them for

Onboarding docs. One link in the welcome email instead of a wiki scavenger hunt.
Multi-part tutorials. Each chapter published separately as the agent writes it, bundled at the end.
Release note archives. A bundle per quarter, chapters per release.
Course material. Chapters are lessons, the landing page is the syllabus.

If the pages themselves still need publishing, start with Add lucid.page to Claude Desktop or the GitHub Action for CI publishing, then bundle what’s worth keeping together.

End