Overview
Workbooks Studio docs.
Workbooks Studio is the hosted workspace for portable interactive workbooks. This is the reference for both Studio (the SaaS) and the open Workbooks standard (the file format and CLI).
What is a workbook?
A workbook is a single .html file that
bundles its own runtime, code, and (optionally) data. Open it in
any browser and it runs — no server, no install, no sign-in.
Workbooks are good for analytical notebooks, interactive documents,
decks, and small apps you want to email rather than deploy.
Workbooks are produced by @work.books/cli. The CLI
compiles a project tree to one HTML artifact and (by default)
embeds a gzipped snapshot of the source inside the artifact itself,
so recipients can workbook unbundle <file> to
recover the project and iterate.
What is Studio?
Studio is the team workspace around workbooks. It adds:
- Group libraries — workbooks organized per team, with contributors and access policy.
- Identity & access — private workbooks gated through the hosted viewer and broker.
- Operational controls — publishing, revocation, tagging, runtime configuration.
- Agent workflows — drive everything from Claude, Cursor, or Codex over MCP.
Studio is the path you choose when "email the file" stops being enough — you want a library, you want to revoke a workbook, you want metrics, you want sign-in. The file you publish to Studio is still a workbook; Studio just hosts it.
Where to next
Start with the Quickstart for a
five-minute path from npm install to a published
workbook. If you're already familiar with workbooks and just want
to move into the team workspace, jump to
Hosting on Studio. If you want to
understand the artifact format itself, read
The standard.