Build a tool once and the request stops coming back to you: the job becomes a template other people fill in themselves, correctly, without you in the loop. Your work is plain HTML, CSS and JavaScript, version-controlled and reviewable, on an open engine, so it stays yours.
New here? Start puts a design system and your first file in place, and How Lolly works shows how a script or an agent uses the same tools as a person. The Glossary defines engine, shell, bridge and tool.
Designers
Set the rules once and keep the tools you already use. What you decide here is what every tool obeys, so a colour or a typeface is fixed in one place rather than argued about per file.
- Import a design - a
.fig,.penpot,.ai,.idmlor SVG file in as an editable layout rather than a flat picture. - Design System Setup - the on-device editor for logos, colours, type and the rest of the design system (
#/start). - Design Tokens and Token workflows - the DTCG token model a design system is made of, and how it moves between tools.
- Authoring Assets - catalog assets, tiers, locales, palettes, themable icons and fonts.
Developers
The app, the CLI and an agent all make the same file from the same inputs, because every input is a URL parameter and every surface runs one render path.
Make files from tools:
- CLI - headless rendering over the same path as the app, driven by
--foo=barpairs. TUI is the interactive terminal shell. - URL Mode - every input as a URL parameter: reserved names, compact encoding and packed links.
- MCP Server and AI Agents - the endpoint an AI agent uses to discover and run tools, and how to drive Lolly from a model.
- Signing from the terminal - give CLI output a real signing identity instead of an anonymous on-device key.
Build tools:
- Build a tool - the guide: manifest, template, styles, hooks, composition and publishing.
- Host API - the
HostV1capability bridge every tool is written against. - Browser extension - capture a live web page as an asset for a tool to compose.
How it holds together:
- Lolly architecture - the engine, the shells, the bridge and the commitments that constrain every change.
- Constraints, Determinism and Reproducibility - why output comes out right, what is byte-for-byte repeatable and how far a bare link carries.
- Data transfer - the
lolly-backupbundle: envelope, integrity and the cross-shell guarantees.
Lolly Work automation
When your organisation runs Lolly Work, automation can run on its server, under its sign-in and policy.
- Organisation jobs - queued renders, batches and approved delivery through Lolly Work's API.
- Lolly Work API and the
lwCLI - manage an instance with its own authenticated permissions. - Invite an agent to a document - give an agent scoped access to one shared document. An invitation does not grant infrastructure access.
Build and contribute
- Get the source - a development checkout sized to what you are here to do.
- Build Guide - build every target: CLI, TUI, desktop, mobile and the web app. Building for iOS adds Apple's extra steps.
- Profiles, brands and tool configuration - profiles, brand packs, capability gating, feature flags and catalog validation.
- Threat Model & Trust Boundaries - what Lolly defends against, what it does not and where each boundary falls.
Hosting Lolly for other people lives in Deploy.