v1.4.0

Read a demo's SHARED.md notes from the CLI and the web client.

• SHARED.md (optional). Put a file named SHARED.md at the root of the repo, on the branch you deploy, for logins, a walkthrough or known issues. Lilypad picks it up on every successful deploy or redeploy (up to 32 KB). Only the demo's creator and Lilypad admins can see it; people who open the demo's URL can't. No file means no notes, never an error. Edits show after the next redeploy. The notes are deleted when the demo is destroyed.
• shared <name> (PowerShell: lilypad shared <name>) prints the notes as the last deploy captured them. | jq -r .message gives the raw file; data has markdown, sha, commit and capturedAt. Creator or admin only.
• Web client
  • A Shared tab in the demo panel.
  • A "Shared notes" menu item and a SHARED.md row on Overview when a demo has notes.
  • Markdown is drawn with no new library and no HTML: HTML in the file shows as plain text, only http(s) links are kept, and images show as links.
• Guidance everywhere: --how-to, lilypad help shared, the setup help, the web guide, FAQ and setup hint, the skill and the README say where the file goes and who sees it.

Needs the platform with ADR 029 deployed. On an older platform, shared fails with an unknown-action error and the Shared tab shows that error. Pin with LILYPAD_VERSION=v1.4.0.

Direct download (no installer). Assets on this release, checked with SHA256SUMS.txt:

• lilypad: bash CLI. chmod +x lilypad, then put it on your PATH.
• lilypad.ps1: PowerShell CLI.
• lilypad-skill.zip: the Claude Code skill. Unzip it into ~/.claude/skills/ to get ~/.claude/skills/lilypad/.
• lilypad.skill: the same skill as one file, for uploading under Skills in claude.ai or the Claude desktop app.

Set the platform URL once with lilypad config url <URL> (or LILYPAD_URL).

v1.3.0

Request metrics and a reworked web dashboard.

• metrics <name> (PowerShell: lilypad metrics <name>). Shows requests in the last hour, 24 hours and 7 days and in total, the 2xx, 4xx and app 5xx counts, p50/p95 response time over 24 hours, and when the last request came in. Creator or admin only. Data lags about 2 minutes, counts requests rather than unique visitors, and "app 5xx" leaves out the load balancer's own 502/503/504 errors.
• status shows the total request count (Requests: N total, data.requests), or n/a if it can't be read.
• Web client
  • A Metrics tab in the demo panel and a Requests row on Overview.
  • Sort by project name (the default), client or status.
  • Group by client, on by default, with demos that have no client last.
  • Card view (the default) or a compact list view. Your choices are remembered in this browser.
  • The client tag now sits on the same line as the project name, at the same size.
  • Fix: the "All clients" filter listed only "All clients", never the clients themselves.
• Skill: documents metrics, data.requests and what to do when the numbers read 0.

Needs the platform with ADR 028 deployed. On an older platform, metrics fails with an unknown-action error and status has no Requests line. Pin with LILYPAD_VERSION=v1.3.0.

Direct download (no installer). Assets on this release, checked with SHA256SUMS.txt:

• lilypad: bash CLI. chmod +x lilypad, then put it on your PATH.
• lilypad.ps1: PowerShell CLI.
• lilypad-skill.zip: the Claude Code skill. Unzip it into ~/.claude/skills/ to get ~/.claude/skills/lilypad/.
• lilypad.skill: the same skill as one file, for uploading under Skills in claude.ai or the Claude desktop app.

Set the platform URL once with lilypad config url <URL> (or LILYPAD_URL).

v1.2.0

Roles, key reuse and estimated cost. Also includes the untagged 1.1.1 changes.

• auth sends your current key again. While your key is valid, lilypad auth <email> emails the same key, so copies on other machines and in the browser keep working. lilypad auth --new <email> (PowerShell: -New) replaces it, and every earlier copy stops working. In the web client, "Send a new key instead" does the same.
• Estimated cost. status shows a Cost: line (data.cost): per month, per day and so far since the demo first went live, at list prices. list shows ~$X/mo for each live demo plus a total (monthlyCost on each row). The web client shows the cost on demo cards, the total in the dashboard header and an "Est. cost" row in Overview. This is a per-demo estimate; the shared platform is not included.
• Roles. whoami shows your role and active-demo cap: user 5, sales 25, elite 50, admin 50. The web client shows the same.
• Admins can deploy and redeploy any demo. The creator gets a note.
• Failure cause (1.1.1). A failed demo's status shows a Last failure: line. redeploy retries a FAILED demo. The web client shows the cause, and warns when a deploy has been stuck for 30 minutes.
• Skill: default size is tiny; cost, roles and --new are documented.

Needs the platform with ADR 024–027 deployed. Without the key secret in place, auth still works but always sends a new key. Pin with LILYPAD_VERSION=v1.2.0.

v1.1.0

GitHub access options, demo notes and build logs.

• GitHub access, three kinds. setup takes a fine-grained PAT, a deploy key (pass the path to its private key file; a .pub file is refused; no passphrase), or public for a public repo. The platform works out which. Source: GITHUB_AUTH (GITHUB_PAT still works) or the hidden prompt, never an option or a conf key. To make a key: ssh-keygen -t ed25519 -N "" -f ~/.ssh/lilypad_<name>, then add the .pub under the repo's Settings > Deploy keys with write access off.
• Notes. setup --notes "text" or NOTES= in the conf file: up to 1000 characters, \n for a line break. Leaving them out keeps the stored notes; --notes "" clears them. status shows them in full, list shows the first 40 characters.
• build-logs <name> [lines]: the latest build's log, running or finished, for the creator and admins. logs now shows only the running app. The web client has a Build log tab.
• Web client: "GitHub access" field with a Load key file button. The field is required when editing a destroyed demo. A Notes box with a counter; the note preview shows on demo cards and the full notes in the Overview. Public /help guide, and setup help in onboarding.
• Default size is tiny.
• CI is green again: shellcheck warnings in tests fixed, and the PowerShell conf check now captures the error.

Needs the platform with ADR 022 (build logs) and ADR 023 (GitHub access) plus notes deployed. Pin with LILYPAD_VERSION=v1.1.0.

v1.0.2

Minor update.

• pin <name> / unpin <name> (admins only): make a running demo permanent (no expiry, can't be destroyed, not counted toward the cap; redeploy keeps it) or put it back on a 30-day lifetime. Needs the platform with ADR 020 deployed.
• Web client: Permanent badge and "Never expires" for pinned demos, Extend and Destroy hidden for them, and a Make permanent / Unpin action for admins.
• Demo cap text corrected to 5 active demos per person (25 for admins) in help, how-to and the web FAQ.

Pin with LILYPAD_VERSION=v1.0.2.

v1.0.1

Minor update.

• Web client (web/): browser version of the CLI with onboarding, dashboard, auto-refresh, live log tail with Clear, setup wizard and admin badge. Served by the included Dockerfile (nginx) as a Lilypad demo.
• whoami help now mentions admin status (the platform reports it).
• list help: it now shows every demo that is not destroyed (set up, building, live, failed).

Pin with LILYPAD_VERSION=v1.0.1.

v1.0.0

Lilypad CLI (bash and PowerShell), installers and Claude skill. Includes lilypad setup --conf (.env-style conf file, --sample, demoproject.sample.conf) and --how-to. Pin with LILYPAD_VERSION=v1.0.0. Licensed under the proprietary license in LICENSE.