new Studio v0.5 — group libraries & broker upload

Ship portable interactive workbooks to your team.

Workbooks Studio is the hosted workspace for the open Workbooks standard. Publish artifacts, organize them into group libraries, manage access, and drive everything from the CLI or an agent.

Open Studio Read the docs

npm install -g @work.books/cli

studio.workbooks.sh / groups / pricing-research

Pricing Research

14 workbooks · 4 contributors · last published 2h ago

Cohort retention v3

notebook updated 2h

Plan comparison tool

app updated 1d

Q3 board deck

deck updated 3d

Discount-curve sim

tool updated 5d

drives from Claude Code Cursor Codex MCP npm GitHub

What Studio adds

The team workspace for the workbooks you ship.

The standard is a file. Studio is the workflow around the file: where it lives, who can run it, how it gets published, who owns it.

◫

Group libraries

Organize workbooks for a team instead of passing files around. Each group has its own library, contributors, and access policy.

◉

Identity & access

Gate private workbooks behind sign-in via the hosted viewer and broker. Self-revoke per workbook. No keys in the artifact.

⌘

Operational controls

Publish, revoke, tag, version. Manage runtime settings, environment values, and workbook metadata from one place.

⌖

Agent-native

The CLI ships an MCP server. Claude, Cursor, and Codex can list groups, publish artifacts, and manage settings as tool calls.

The open standard

A workbook is one HTML file. Always.

A workbook is a portable HTML artifact for notebooks, apps, decks, documents, and tools. Build it with the CLI, host it in Studio, or keep it as a file you can email, archive, inspect, and run locally without ever signing in.

Portable runtime. The output is a browser-runnable .html.
Source-aware. Builds embed a gzipped source snapshot so recipients can unbundle and iterate.
Framework-friendly. Author in Svelte, React, vanilla HTML, MDX — anything that compiles to the browser.
Studio-optional. Studio adds hosting; nothing about the file requires it.

Read the spec Source on GitHub

my-workbook.html

<!-- everything in one file -->
<!doctype html>
<html>
  <head>
    <meta name="wb-permissions" content="net">
    <style> … </style>
  </head>
  <body>
    <!-- your app code, inlined -->
    <script type="module">
      render()
    </script>

    <!-- bundled source travels along -->
    <script id="wb-source-bundle"
            type="application/x-workbook-source">
      eJzNVk1v2zAMvfdXEN6h…
    </script>
  </body>
</html>

Agent-native

Drive it from Claude, Cursor, Codex.

@work.books/cli ships an MCP server. Point any MCP-aware client at it and an assistant can list groups, scaffold projects, publish artifacts, and manage runtime settings as structured tool calls — no scraping, no glue scripts.

For Claude Code specifically, install the official Workbooks skill so it knows the standard, the Studio workflow, and the CLI commands without prompting.

Agent setup Claude Code skill

.mcp.json

{
  "mcpServers": {
    "workbooks": {
      "command": "workbook",
      "args": ["mcp", "serve"]
    }
  }
}

Start with the file. Scale with Studio.

Build a workbook in five minutes. Move it into a group library when you're ready to share it with the rest of the team.

Open Studio free during private beta