Venom Studio
Make slide decks, pages and HTML pages from blocks and charts, change one slide or block at a time, keep every version, and share by link, from the console or from an agent.
Venom Studio is where your organisation makes, stores, versions, shares and presents artifacts: slide decks, pages (a report, a one-pager, a dashboard) and free-form HTML pages.
An artifact is data, not HTML. A deck is a list of slides, each a layout plus a few slots of content. A page is a list of blocks. Venom draws them with your organisation's theme, so neither you nor an agent writes CSS or boilerplate, and a chart is a few lines of data instead of a screenshot. That is what makes it quick to iterate on, and cheap for an agent: it reads an outline of ids and titles, then changes one slide or block by its id without sending the rest again.
- The Studio pages: the list with previews, the viewer, the light editor, present, print, share and history.
- What Studio makes: decks, pages and HTML pages, ownership, sharing and the limits.
- Blocks and charts: the component library, with a spec for each block, chart and diagram.
- Slide layouts and themes: the thirteen layouts, the built-in themes and your own.
- Edit by id: anchored edits, batches, versions and the version check between two writers.
- Share, present and print: who sees an artifact, public links, present mode, print to PDF, and why an HTML page is sandboxed.
- Studio for agents: the
studio_*MCP tools and the REST API.
In this section
- What Studio makes: The three kinds of artifact (deck, page, HTML page), who owns and sees them, the limits, and where Studio keeps what you make.
- The Studio pages: The list with previews, the viewer, the light editor with a live preview, present mode, print, the share dialog, version history and theme settings, and how to reach Studio from the rail, ⌘K and Home.
- Blocks and charts: Every block a page or slide can hold, with a spec for each text, table, chart and diagram block, and how Venom checks a spec.
- Charts, tables and KPI components: The data components an agent fills with numbers instead of drawing anything, the one data contract they share, the shapes Venom also reads, and how to place them in a page, a deck slide or an html page.
- Slide layouts and themes: The thirteen slide layouts and their slots, the built-in themes, how to set your organisation's own colours, fonts, logo and corner radius once, one artifact's own tweaks, and themed HTML pages.
- Header, footer and marks: Put your company, logo, author, date, a confidentiality label, a header, a footer and slide numbers on decks, pages and html pages, on screen, in print and in PowerPoint, with organisation defaults each artifact can override.
- Edit by id: Change one slide or block without resending the artifact, in batches that apply all or none, with a version for every write and a check that stops two writers overwriting each other.
- Share, present and print: Who can see an artifact, public share links you can revoke, present mode with notes, printing to PDF, PowerPoint downloads, and why a free-form HTML page runs sandboxed.
- Research runs: How Studio researches and writes a report on the server — plan with goals, parallel researchers over Venom Search, scholarly works and World Bank data, an analysis per section, the build and a review — with the intensity and agent controls, budgets, and what happens when research is off.
- Studio for agents: The studio_* MCP tools and the REST API, the cheap workflow that keeps an agent's token use small, and what each answer returns.