# Publish your story

Use this guide when a story plays the way you want in Canvas and you want a public link. You will publish it, open the link, and watch each path the way a viewer does.

## Before you start

You need a story in Canvas that plays to an ending on every path. Canvas saves your changes by itself, so the File you have open is the one that publishes. Play each choice with **Preview** before you publish.

## What becomes public

When you publish, Bitebox makes a page for the project at `https://bitebox.gg/play/<project id>`. Anyone with the link can open it and play the story without signing in.

The page shows:

- The story from the File you have open, as it was when you published. Canvas-only details, such as where nodes sit on the canvas, are left out.
- The clips the story plays.
- The page text and images: the title, the overview, the episode title and description, the "How it Plays" summary, the cover, the logo, the other images and the genres.
- The "How it Plays" facts, which Bitebox works out from your story. They show if the story branches, how long it plays (a range, such as 3–5m, when paths differ), and how many choice points the story has across all its paths. A choice counts only when a path reaches it and at least one of its options leads on or ends the story. The length shows only when every clip on every path that ends has a known length, and the story has no loop. A hidden choice does not count toward the length or the paths. The length is also not shown when a choice is set to appear after its clip ends. When a Timer, or a choice or target set to Instant, leaves a clip before its end, the length counts only the part a viewer watches: up to the Timer, or from when the choice appears to when it closes. The length is not shown when Bitebox cannot tell when a clip is left: for example a chat, which leaves whenever the viewer answers, an Instant option that ends the story partway through a clip, a clip with a Timer and another choice or target on it, or a Crossfade between clips.

Changes you make in Canvas after you publish do not change the page. Publish again to update it. Share the link only where you have the right to show the clips.

## Publish from Canvas

1. Open the project in Canvas.
2. Select **Publish** at the top right. A preview of the public page opens. The top right of the preview says **Unpublished**, or when you last published.
3. If some page text or images are empty, Bitebox fills them in. A status label shows while it works. Wait until it goes away.
4. Optional: select a title or description in the preview to type your own. Use the upload icon on the cover or on the logo to add your own image. To get a new logo from Bitebox, select the logo and select **Regenerate logo**. Each project gets three logo draws a day. The page colors follow the cover image.
5. Use **Desktop** and **Mobile** at the top to see the page at each size.
6. Select **Publish** at the bottom right.

Canvas opens the public page in a new tab. The tab waits until the page is ready, then shows it. The next time you open **Publish**, the preview says when you last published. If the new tab does not open, the page is still published. Allow pop-ups for Canvas to open it from **Publish** next time.

## Watch both paths

1. On the public page, select **Play Now**.
2. When the choices show, select one. Watch the path to its ending.
3. Reload the page and select **Play**. When the choices show, select a different one. Do this until you have watched each choice.

At the end of the last episode, select **Replay** under the synopsis. The story starts again at its first clip, and plays in order to an ending. The end bar and **Replay** come back at every ending, on a published page and on a preview link. On a phone, the story's title and synopsis stay hidden while one clip moves on to the next. Tap the picture to show them.

If a choice leads to a Storyline that isn't connected, or a clip does not play, fix it in Canvas, check it with **Preview**, and publish again.

When playback copies are enabled, the player uses a ready copy of each clip.
If a copy cannot load, every video using it falls back to the original clip.

## Follow a series

On the public page, **Follow** sits beside the episode title. A signed-in viewer's click switches it to **Following** once the account has saved the series. That pill matches **Follow**, with white and black swapped, and the same icon. A signed-out click asks them to sign in with **Continue with Google** or **Continue with Email**. The email has a 6-digit code: typing it signs them in and reloads the page at the same place. Either way the series is already **Following**, and the story is paused where they left it, with Play. They do not select Follow again. The series page has the Bitebox header at the top: the Bitebox logo, which goes to bitebox.gg, then **Sign in** and **Start creating**. A viewer already signed in to Bitebox (in Canvas, say) is signed in here too. After a viewer signs in on the story page, Canvas opens Home as the same account. Once signed in, the header shows **My projects** and the viewer's picture (or the first letter of their email); select the picture to see the account and **Sign out**. **Sign in** opens the same sign-in sheet as Follow and keeps the viewer on the story. **Start creating** asks a signed-out viewer to sign in, then opens Bitebox. While the player chrome is up, **Create** and **Sign in** (or the picture) sit at the player's top right.

Bitebox remembers that account as following the series, and remembers which endings of the episode they have finished. At the end of a finished series, the bar under the synopsis reads that count. A guest's finished endings move onto the account when they sign in. The browser also keeps the endings it finished, so the bar shows the share even when the viewer has no session or the count cannot be read. **Create** in the player opens Canvas in a new tab.

Bitebox also saves the viewer's place in the story as they play. If that place cannot load or save, a line at the top of the story says so, and **Retry progress** tries again. The story keeps playing while the line shows.

## Go back to an earlier version

Canvas has no button that takes a page offline. Moving the project to Trash also keeps the published page public.

To put an earlier version on the page:

1. In Canvas, select the Bitebox logo at the top left to open the **Projects** menu, then select **Earlier versions**. Saves are listed newest first.
2. Select the save you want, then select **Restore as new save**. Select **Restore** to confirm.
3. Check the restored story with **Preview**.
4. Select **Publish** and publish again.

The page then shows the restored version. Your newer saves stay in **Earlier versions**.

## Publish through your assistant

An assistant cannot make a page public on its own. It asks, and you confirm in Canvas.

1. The assistant checks the paths with `playthrough_simulate`.
2. It runs `publish_check` on the File. The check looks at each route a viewer can take, the choice timing and the size of the public story. A story may loop back as often as you like: the check follows each route once, so a story with thousands of paths can pass. Each failure names its fix.
3. Optional: it drafts page text with `publish_copy_generate` and saves what you like with `publish_copy_set`. `publish_copy_get` shows what the page holds now.
4. It sends `publish_request` with a one-line summary of the story for the page. Nothing is public yet.
5. Open the project in Canvas. A card, **Agent request**, shows under **Publish** with the assistant's name.
6. Select **Watch** on the card to play the exact version it will publish.
7. Select **Publish** on the card, or **Not now** to cancel the request.

The card keeps **Publish** off until that version has a passing `publish_check`. After your click, the card shows "Your page is public" and the link. The assistant reads the same link with `publish_status`. A request you do not confirm expires after one day. A project has one open request at a time. While your click publishes it, the assistant cannot send another one.

To go back, the assistant sends `publish_rollback` with an earlier published version. That also waits for your click on the card.

One exception exists, for NEUKO team accounts only. Such an account can let its own assistant publish without a click, after a passing `publish_check`. The consent screen does not offer this. Every other connection asks you to confirm each publish.

## Check and fix

When Preview, Publish, Save or Duplicate cannot run, the reason shows in a message at the bottom of Canvas.

- **Preview, Publish or Duplicate says "Your latest edits are still saving. Try again in a moment."** Bitebox opens only work that is saved. Wait a few seconds, then select it again.
- **The card's Publish stays off.** Ask the assistant to run `publish_check` on the version the card names, and fix what fails.
- **The assistant says it cannot publish.** The connection may not allow publishing. Open the **MCP** tab on your Canvas home page and check its publish setting. [Troubleshooting](/docs/mcp/troubleshooting) explains refusals such as a missing permission.
- **A card says "This node needs the package ..., which isn't available here."** Bitebox keeps that card and everything in it in your File, through every save. It cannot play or publish the card. When you play the File, the story stops at that card with "This part of the story isn't available right now." `publish_check` fails with "This File holds data that cannot be published yet" and lists the ids of those cards. To publish, delete those cards and the `packages` list in the File's JSON, or ask your assistant to do it. Then check again.
- **A viewer's link says "This story isn't available."** The story has no live version, or the link is wrong. Check that the link matches the one on your publish card, and that the story is still published. Sign in on bitebox.gg to get an **Open in Canvas** link on that page.

## Ask your agent

> Help me publish my Bitebox story in project [project name]. First, inspect the project with workspace_context and playthrough_simulate, and tell me each path and the ending it reaches. Run publish_check and fix what fails. Explain the proposed changes and ask before you send publish_request.

Review the card in Canvas, and select **Watch** before you select **Publish**.

## Related pages

- [Sign-in, consent and access](/docs/mcp/access)
- [Tools](/docs/mcp/tools#publish)
- [Troubleshooting](/docs/mcp/troubleshooting)

---
Source commit: 9ccaa86d41d7 · Build date: 2026-11-17T03:27:39.423Z
