Lolly
啟動應用程式
  1. 自動化
  2. URL 與 CLI 自動化

App links and deep links

Links open a tool, a shelf of Assets, a Projects folder, a room of Lolly Design System Setup or one card in Settings. Use them in a launcher, a bookmark, a bug report or an automation that must open the app in a known state. Every screenshot in these docs is a Lolly link handed to url-shot.

The lolly:// scheme

The installed apps register the lolly:// URL scheme. Anything that can open a URL can then open Lolly at an exact place: a launcher's "open URL" action (Raycast, Alfred, PowerToys Run), a macOS Shortcut, a .desktop Action, a GNOME Shell or KRunner result, a link in a note, a QR code on a slide or a terminal.

On the web

https://lolly.tools/t/qr-code?url=https%3A%2F%2Fexample.com&full

Opens in a browser, for anyone.

In the installed app

lolly://t/qr-code?url=https%3A%2F%2Fexample.com&full

Launches Lolly, opens QR Code with its url filled in and hides the sidebar.

lolly://<route> is https://lolly.tools/<route>. The query holds the same tool inputs and reserved words as the web form. Presence flags such as full need no =1, and z= and zx= are the same packed and encrypted state. Readable flags after them still win.

open      "lolly://t/qr-code?url=https://example.com"     # macOS
xdg-open  "lolly://t/qr-code?url=https://example.com"     # Linux
start     "lolly://t/qr-code?url=https://example.com"     # Windows

Every tool form works: lolly://t/<id>?…, lolly://tool/<id>?…, a bare lolly://<id>?… and the embed form lolly://tool/<id>.svg?…, whose extension becomes format=. Any app route works too, such as lolly://lab, lolly://verify?asset=lolly/logo/primary or lolly://docs/build/authoring-tools. A web link with https:// swapped for lolly:// keeps working: the app drops the lolly.tools host instead of reading it as a tool id.

The Share dialog writes this form for you. Open Link options and turn on Open in the installed app. The field and its Copy and QR actions switch to lolly:// and keep the same state, password or packing and behaviour flags. Turn the option off to return to the web link. The web link stays the default, for a recipient who may not have Lolly. The app link is for shortcuts and automation.

A link for a route the app does not own is refused, not guessed at. The operating system hands the app an untrusted string. The app therefore opens only a tool id that parses or a word from its fixed list of routes, and refuses any other link. A lolly:// link also works where the app accepts a Lolly link: the asset picker, the pasted-link paths and the CLI's lolly <link> form.

Where the scheme is registered

The macOS and Windows installers, the Linux .desktop entries and the Android and iOS apps declare the scheme. A tauri dev build registers itself on Windows and Linux at launch. On macOS only the installed .app can receive the scheme. Spotlight opens web addresses but not custom schemes, so on a Mac use open, a Shortcut or a launcher.

The MCP server's resource URIs (lolly://catalog, lolly://tool/{id}) share the prefix but are a different namespace: resources an agent reads, not routes the app opens.

The address bar and Share make two different links.

In both links, an explicit off value or a cleared field reopens unchanged. Long text is not cut short.

  • Every input value you set, unless it is personal
  • Token references, which redraw in the recipient's design system
  • Theme and colourway choices (_themes), emoji set and licence
  • Result settings and the link options you tick

Stays on your device

  • Personal values you did not choose to include
  • Images you uploaded (user/… ids) and files held in memory
  • Saved-session names (slot), which reopen only where the session exists
  • Your design system choice (ds, designv), drafts in Settings forms, file-picker selections and live camera or microphone streams

Personal values need your say. A generated link leaves out inputs bound to your profile and inputs a tool declares with sharePrivacy: "personal", such as recorded speech and caption text. The Share dialog shows those values on your device and asks you to include each one separately. The address bar leaves them out as well.

These rules change only what a generated link holds. A link that sets a personal input explicitly still loads that input. The CLI still accepts every input, and your saved sessions keep the original values.

警告: A shortened link is not a locked one

A shortened link holds its values in readable form once unpacked. Password protection is a separate choice (Encrypted links).

When the bytes must travel, send a file. Share reports the local dependencies a link leaves out. A .lolly file carries the saved design to another device, with the files Lolly can include, such as your uploaded images. The file is separate from the generated link. Review the file before you send it on.

  1. The address is live. A view reads its parameters when it opens and writes them as they change. Input edits and filters replace the current history entry. Moving between views adds a Back stop. Pasting another query for the same view applies that query too.
  2. A link does not change your preferences. A link's sort order, view mode, open cards or appearance applies to that visit only. Changing a control yourself can still save the choice.
  3. Unknown values are ignored. A parameter that points at nothing, such as a retired category or a mistyped section, is dropped and the view opens as usual.

App views

App-wide

ParamDescription
langInterface language for this session, on any route (#/a?lang=ja, #/settings?lang=ar). Same values and rule as the tool-route lang.
themelight, dark or brand for this page load only. Never saved to the profile or the browser. App views only: on a tool link (/t/<id>, #/tool/<id>, /design) the app ignores this parameter, because several tools have a theme input of their own.
_appearanceThe app's appearance, tool routes included. Takes the same values as theme and wins over theme. Written by the appearance control and left out of a content Share link.
_open=<id>,<id>Open disclosure cards in Settings, Components and Lolly Design System Setup. An empty _open= closes every addressable card.
ParamDescription
qFills in the search field.
catThe category pill to open on: all, favourites or a category key the pills show on that install. Feature flags and the Utilities view already narrow that set.
sortrecent, az, za, format or category, for this visit only.
dirasc or desc.
tool=<id>Opens that tool card's info dialog over the gallery.
history \history=<id>Opens a tool's saved-sessions dialog instead of the info dialog.
welcomePresence flag: opens the first-run welcome dialog for capture, even after a dismissal. Ignored on branded and brand-locked installs, which already have a design system.

Assets (#/a)

The server paths /a and /assets open the same view. #/c, #/catalog and /c forward here with their query, so #/c?asset=<id> still opens that asset.

ParamDescription
asset=<id>Scrolls to and highlights that asset.
swatch=<label>Opens that brand swatch's details, the link a swatch's Copy link writes. asset wins when both are given.
section=<key>[,<key>…]Opens with those sections expanded and scrolls the first into view. An empty section= closes every section.
qFills in the search field.
typeFiletype filter: all, image, vector, motion, audio or text. Falls back to all when that group is empty on this install.
hiddenPresence flag: shows hidden assets.
sort, revSort key and direction (rev=1 reverses, rev=0 keeps the usual direction).
view, favouritesThe preview strip mode and whether the favourites strip is open.

Search, type, sorting, asset focus and sections keep one another in the address.

Projects (#/p, #/p/<folderId>)

ParamDescription
qShows results for that search.
toolsNarrows to sessions of those tools.
viewpreview (tile grid) or list.
sortmodified, added, name, tool or size.
revReverses the sort; rev=0 keeps the usual direction.

view, sort and rev override both the device-wide and the per-folder saved preference on arrival. Changing the controls updates the address.

Batch and Lolly Multi-edit

#/batch?s=<slot>,<slot> opens those saved sessions as rows in the grid. Edit as sheet builds this link. #/pro, the route's name before 2026-08-20, and the /pro path still redirect here with their query.

#/multi?s=<slot>,<slot> opens those sessions side by side, and _active=<slot> records the active cell. These session ids resolve through this device's storage.

Lolly Design System Setup (#/start)

ParamDescription
areaWhich room, by its key: overview (Board), color (Colours), type (Type), logos (Logos), tokens (Tokens), catalogue (Files), usage (Rules), skills (Skills) or versions (Versions, which this link opens even before a first publish adds the room to the strip).
focusA wing of the colour room: generate, curves, contrast, print or chart. Three more open a first decision: pick (the Colours room's colour picker), stage (the Type room's face stage) and looks (Find a look, ready-made colours and type).
seed=<hex>Sets the Generate wing's primary colour before it opens.
wheelPresence flag: opens the OKLCH colour chart, the same as focus=chart.
importPresence flag: opens the source picker on arrival (import=0 keeps it shut).
sourceWhich source the picker opens on: file, image, font, pdf, page or url. Naming one opens the picker. Nothing is fetched or read on your behalf.

Room, wing and source-picker changes update the address. seed and wheel act once, on arrival. Opening a source link never restores an unsaved file selection or starts a read.

Settings (#/settings)

#/settings?tab=<tab> opens one tab: device (This device), brand (Design system), caps (Capabilities) or activity (Activity & stats). With no tab, Settings opens on Preferences. #/b and #/brand are shortlinks to the Design system tab. The older #/d route reads tab and the section ids below, and the older #/profile route reads focus.

Settings navigation writes focus, card toggles write _open and the settings search writes q. Moving between tabs adds browser history entries.

The remaining views

Routes and their parameters
RouteParams
#/verifysrc=<path> checks a file served by this site. Only an absolute same-origin path is accepted, because the page fetches nothing on your behalf. check=1 with src also resolves the credential reference the page shows, without the second Fetch and check click.
#/openlolly=<path> opens a .lolly served by this site (an absolute same-origin path starting with a single /) or a blob: URL the same page made. data:, javascript:, //host and every other origin are refused before anything is fetched. The address becomes a bare #/open before the fetch, so a reload never imports the file twice. A plain saved design opens straight into the editor. A file that carries a tool, a design system, templates, a renovation or a project still asks first, as a drop does. Nothing in the link grants trust. The route is for automation (lolly run <file.lolly> --export=… uses it) and is not a lolly:// route.
#/docs/<slug>Renders in the app's current language; #/docs/<lang>/<slug> or ?lang= picks one. ?h=<heading> jumps to a heading.
#/ask?q=<question> fills in the question box.
#/lab?c=<any CSS colour> opens the Lolly Colour Lab on that colour.
#/componentsq, mode and section restore its search, mode filter and section focus.
#/historyFilter keys keep their current values; _detail=<slot> opens the versions sheet for that local session.
#/learningslot opens a local learning module; _lesson and _blocks restore the selected lesson and blocks.

On a tool route

Most tool-link flags are in Reserved URL parameters: options, full, template=<id>, slot= and present with s= and kiosk. A bare ?template= opens the template chooser. The gallery's +New chip links there. The one exception is share, a presence flag that the tool view reads instead of the engine. The flag opens the Share dialog on load.

Canvas editors keep EDITOR state in _sel=<id>,<id>, _t=<seconds>, _panel=choreograph or _ui=. The first three select boxes, seek the timeline and open Choreograph. The object form is base64url UTF-8 JSON, for example { "v": 1, "sel": ["a", "b"], "t": 2.5, "page": "page-1", "timeline": true }. Fields are optional. Unknown keys are ignored, and shorthands win on conflict. Selection, page, playhead and timeline visibility update the address through _ui. An empty selection and timeline:false are explicit state. window.lolly.ui.getState() and apply(state) use the same object, as does a trusted embedding page's postMessage({ type: 'lolly:ui', state }).

The shell also writes three more workspace keys: _view for the stage viewport, _dialog=share while the Share dialog is open and _nav with _inspector for Lolly Design's columns. These workspace keys stay outside packed content, so a delayed pack cannot overwrite newer view state. They never enter a content Share link. The engine reserves the _ namespace, so tool inputs cannot collide with these keys.

Section links from the earlier guide