Skip to main content

Chapter 8: Bundling Your Pack

TL;DR​

  1. Stop worka dev (Ctrl+C in the terminal).
  2. Build a release artifact: 
    worka build --release
  3. Publish to the Worka registry via a pull request.

Throughout this tutorial, you used worka dev for fast iteration. Now it’s time to create a production artifact.

Step 1: From Development to Production​

The worka dev server is optimized for speed and hot-reloading, not for creating a final asset. For that, we use the bundle command.

First, stop the development server by pressing Ctrl+C in the terminal where it is running.

Step 2: Build the WASM artifact​

In your pack’s root directory, run:

worka build --release

This builds a production WASM artifact (main.wasm) along with the pack manifest.

Step 3: Publish​

Worka packs are distributed through the official registry repository. For MVP:

  1. Build your pack to produce main.wasm.
  2. Create a GitHub release for the pack (the release hosts the WASM).
  3. Open a pull request to worka-ai/registry updating the pack entry to point at the release.

The Worka app installs packs by reading the registry entry and downloading the WASM from the release URL.

Note: Third‑party registries (including private registries) are supported for teams that want fully private packs.

Congratulations! You have completed the end‑to‑end cycle of a Worka pack:

  • Set up your environment.
  • Scaffold, run, and view a pack in development.
  • Build A2UI views with the SDK.
  • Implement tools in a pack MCP server.
  • Produce a release artifact and publish it.

In the following parts of this guide, we will move from this tutorial format to a more detailed exploration of specific topics, diving deeper into the powerful features of the Worka platform.