droppageAccount

Changelog · human and machine readable

What changed in droppage.

Short release notes for analysts, developers, and agents sharing interactive HTML. Agents should read the JSON feed at session start or weekly. People can get them by email.

  1. Compatible update

    The MCP server has a registry name

    CLI 0.5.1 carries the name io.github.Vilancer/droppage so the local MCP server can be listed in the official registry. Commands are unchanged from 0.5.0.

    • Update the CLI to 0.5.1 (droppage upgrade). The server is still started with npx -y droppage mcp after droppage login. Nothing about publish, update, access, or stdout changed.
  2. Compatible update

    Publishing an email page invites the people on it

    From CLI 0.5.0, droppage upload --email and the MCP publish_page tool email each listed person an invitation with an access link as soon as the page is live. Before, publishing emailed nobody and each person had to ask for a link at the page.

    • Update the CLI to 0.5.0 (droppage upgrade). droppage upload report.html --email a@x.com,b@y.com publishes, then queues one invitation per address; stderr shows droppage: 2 invitation(s) queued: a@x.com, b@y.com. stdout is still only the page URL. droppage recipients list <slug> shows each invitation as queued, then sent.
    • To publish now and invite later, add --no-invite, then run droppage recipients invite <slug> when ready. recipients invite emails everyone on the page who has never had an invitation and skips the rest, so it is also the retry if sending failed; recipients resend <slug> <email> sends one again.
    • Over MCP: publish_page takes invite (default true) and returns invited, the addresses invited; the new invite_recipients tool does what recipients invite does. If the invitations cannot be queued, the page stays published and the warning says how to send them.
    • Private pages, password pages and public pages email nobody, as before.
  3. Compatible update

    Keep a separate session with DROPPAGE_HOME

    CLI 0.5.0 reads DROPPAGE_HOME: the folder that holds the login session and the release-check cache, instead of ~/.droppage. Scripts, CI and test setups can sign in separately without touching your own session or changing HOME.

    • Update the CLI to 0.5.0 (droppage upgrade). DROPPAGE_HOME=/tmp/droppage-ci droppage login signs in with a session in /tmp/droppage-ci/config.json (mode 0600); every later command with the same DROPPAGE_HOME uses it. Unset, the CLI keeps using ~/.droppage as before. It also works for the MCP server: pass DROPPAGE_HOME in the server env.
    • DROPPAGE_HOME is read only from the real environment. A DROPPAGE_HOME line in a project's ./.env is ignored, so a repository cannot move your session into its own folder.
  4. Compatible update

    Docs, changelog, and feedback have their own pages

    droppage.dev is split into pages: the homepage for what droppage is and what it costs, droppage.dev/docs for the commands and the agent setup prompt, droppage.dev/updates as the changelog with the email sign-up, and droppage.dev/feedback. No CLI change.

    • The "Setup droppage for your agent" prompt, the command list, and the agent output contract are at https://droppage.dev/docs (#commands, #agents, #faq). The homepage keeps a short summary that links there.
    • The changelog is https://droppage.dev/updates, now in the site menu; subscribe to product updates by email at https://droppage.dev/updates#subscribe. The JSON feed is unchanged: https://droppage.dev/updates.json.
    • Feedback from people goes through https://droppage.dev/feedback; agents keep using droppage feedback or POST /api/feedback, unchanged.
  5. Compatible update

    Publish from MCP clients with droppage mcp

    CLI 0.4.0 adds droppage mcp, a local Model Context Protocol server on stdio. Agents publish, update, list, expire and delete pages, manage recipients and media, check the quota and send feedback through typed tools, signed in with the droppage login session.

    • Update the CLI to 0.4.0 (droppage upgrade), sign in once with droppage login, then add the server. Claude Code: claude mcp add droppage -- npx -y droppage mcp. Cursor (.cursor/mcp.json), Windsurf and Claude Desktop: {"mcpServers": {"droppage": {"command": "npx", "args": ["-y", "droppage", "mcp"]}}}. Codex (~/.codex/config.toml): [mcp_servers.droppage] with command = "npx" and args = ["-y", "droppage", "mcp"].
    • Tools: publish_page (a file path or inline html; access public, email or private; emails; expires), update_page, list_pages, delete_page, set_page_expiry, get_quota, list_recipients, add_recipients, remove_recipient, upload_media, list_media, delete_media, send_feedback. Results are JSON with a warnings list. update_page, delete_page, set_page_expiry, remove_recipient and delete_media are marked destructive, so clients ask before running them.
    • Signed out, tools answer "Not signed in. Ask the user to run droppage login in a terminal, then retry." There is no password mode over MCP, so passwords never land in an agent transcript: for a password page, run droppage upload <file> --password in a terminal. Inline html cannot bring local images or videos; pass a file path for those. Publishing an email page emails nobody: each person enters their email at the link to get an access link, while add_recipients emails new people an invitation (the agent instructions said otherwise before; they are corrected).
    • list --json rows now include expires_at, as the documentation already said. Every other CLI command and its output are unchanged.
  6. Compatible update

    Machine-readable docs at droppage.dev/llms.txt, and a design skill for agents

    Agents and doc tools such as mcpdoc can read droppage.dev/llms.txt (an index in the llmstxt.org format) and droppage.dev/llms-full.txt (the agent instructions and the CLI README in one file). No CLI change.

    • https://droppage.dev/llms.txt links the agent instructions for Codex, Cursor, Claude-style and other agents, the agent pack manifest, the CLI README, this updates feed, and the npm package.
    • https://droppage.dev/llms-full.txt holds the full agent instructions and the CLI README as plain text. Both files are generated from the published agent pack, so they always match it.
    • To use them from an MCP client, point mcpdoc at the index: uvx --from mcpdoc --with "mcp<2" mcpdoc --urls droppage:https://droppage.dev/llms.txt --allowed-domains https://raw.githubusercontent.com/ --transport stdio. The --allowed-domains flag lets fetch_docs open the linked instruction files; mcpdoc does not run with the mcp 2.x Python package yet, hence the pin.
    • The agent instructions now ask agents to load Anthropic's frontend-design skill before they build or restyle a page, and to suggest it when it is not installed. Claude Code: /plugin install frontend-design@claude-plugins-official; Codex, Cursor, and other agents: its SKILL.md from https://github.com/anthropics/skills/tree/main/skills/frontend-design.
  7. Compatible update

    Pages host their own videos

    CLI 0.3.0 uploads local MP4 and WebM videos a page references, the same way as images: same URLs, same per-page budget, deleted with the page. Videos play in every browser, including Safari and iOS, and can be seeked.

    • Update the CLI to 0.3.0 (droppage upgrade). upload and update pick up local videos in <video src>, in <source src> inside <video>, and the poster image in <video poster>, upload them to the page and rewrite the links to https://droppage.dev/i/<id>.mp4 or .webm. stderr shows one droppage: video … → … line per video; stdout is still only the page URL. Same folder rule as images: paths relative to the HTML file and inside its folder.
    • Each video can be up to 20 MB and is checked by its file signature, not its name: MP4 (H.264 plays everywhere) or WebM (VP9). .mov and .mkv files are refused; convert them first. Videos count in the same per-page budget as images (Free 5 MB, Starter 20 MB, Builder 50 MB) and their traffic counts toward monthly bandwidth. Plan limits are unchanged.
    • Videos are served with HTTP Range support (206 Partial Content, Accept-Ranges: bytes), which Safari and iOS need to play a video and every browser uses to seek. Like images they are public to anyone with the URL, are not covered by a page's password or email gate, are removed by update when the HTML stops using them, and are deleted with the page or at its expiry.
    • For a short muted loop: <video autoplay muted loop playsinline poster="still.webp"><source src="film.webm" type="video/webm"><source src="film.mp4" type="video/mp4"></video>. There is no need to inline a film as base64 any more. droppage image upload film.mp4 --page <slug> (or its new alias droppage media upload) adds a video to an existing page.
  8. Compatible update

    More local images come along, and images load faster

    CLI 0.2.2 uploads local images referenced in srcset, icon links and <style> url(), not only <img src>. update no longer removes images that the new HTML links to, and images are now cached close to visitors.

    • Update the CLI to 0.2.2 (droppage upgrade). upload and update also pick up local images in srcset on <img> and <source> (every candidate, descriptors kept, e.g. <picture><source srcset="hero-m.webp 1x, hero-l.webp 2x">), <link rel="icon"|"apple-touch-icon" href>, and url(...) inside <style> blocks. The folder rule is unchanged: paths relative to the HTML file and inside its folder. style="..." attributes and .ico files are not picked up.
    • Fixed: droppage update could remove images that the new HTML links to (for example images added with droppage image upload --page and then written into the HTML), because the clean-up step could read the previous version of the page. It now removes nothing until it reads back the HTML that update stored.
    • Images are cached at the edge: a page with many images loads faster for every visitor after the first. A deleted image, or one whose page was deleted, stops being served within 5 minutes; an expiring page's images stop at the expiry time (within 5 minutes if the expiry is moved earlier). A browser that already loaded an image may keep it up to a day.
  9. Compatible update

    Page slugs never start with a dash

    About one page in 64 got a slug starting with "-", which the CLI then read as an option, so update, expire, delete and recipients failed for it. CLI 0.2.1 never makes such a slug and explains the workaround for older ones.

    • Update the CLI to 0.2.1 (droppage upgrade). New slugs start with a letter or a digit.
    • For an older page whose slug starts with -, put -- in front of the slug, with any options before the --: droppage expire -- -AbC12xYz9 never, or droppage update --expires 7d -- -AbC12xYz9 report.html. Without it the CLI fails with "unknown option" and now prints this hint on stderr.
    • Existing links, slugs and output are unchanged.
  10. Compatible update

    Agent instructions for sharing reports and dashboards

    The agent packs, the homepage setup prompt, and the README now describe when and how to publish analytics reports and dashboards for other people. No CLI change.

    • Use droppage when the user wants other people to see an analysis: a team dashboard, a weekly KPI or stakeholder report, a client deliverable, a notebook or BI export, a data story, or model results.
    • Build one self-contained HTML file, up to 5 MB, with the data and CSS inside it. Scripts run and chart libraries can load from a CDN; jupyter nbconvert --to html, Plotly write_html(include_plotlyjs="cdn"), and Altair chart.save() output can be published as is. Pages are sandboxed: no localStorage, cookies, or same-origin requests.
    • Choose access deliberately: --email for named stakeholders (Builder, managed later with droppage recipients add|remove), --password for a group link (Starter and Builder), --private for a draft, public only when the user says so. On the Free plan, pages can be public or private, without a password or email list.
    • Recurring reports: droppage update <slug> keeps the same link and access settings. One-off deliverables: --expires 30d. list --json rows have view_count (unique visitors) and last_viewed_at.
  11. Compatible update

    Pages carry their own images, can expire, and count unique visitors

    Local images referenced in the HTML are uploaded with the page and deleted with it. Pages can expire with --expires or droppage expire. A view is now one unique visitor per page, and signed-in owners open their own protected pages directly.

    • Update the CLI to 0.2.0 (droppage upgrade) for images and expiry. Reference local image files in <img src> (paths relative to the HTML file, inside its folder; no ../ or absolute paths) and run droppage upload: the CLI uploads them to that page, rewrites the links to https://droppage.dev/i/<id>.<ext>, then publishes. stderr shows one line per image; stdout is still only the page URL. droppage update uploads new images, keeps the URL of an unchanged image, and deletes the ones the new HTML no longer uses.
    • Images belong to their page and are deleted with it. Per-page image budget: Free 5 MB, Starter 20 MB, Builder 50 MB; each image up to 4 MB; PNG, JPEG, GIF, WebP, AVIF, SVG. Image traffic counts toward monthly bandwidth. Prefer WebP or AVIF for photos and SVG for charts; the CLI prints a tip on stderr when a PNG, JPEG, or GIF is over 300 KB.
    • Hosted images are public to anyone with the URL and are not protected by a page's password, email, or private gate. Inline sensitive images as data: URIs instead. Advanced: droppage image upload <files> --page <slug>, image list [--page <slug>] [--json], and image delete <id-or-url> manage a page's images directly.
    • Pages can expire, on every plan: droppage upload report.html --expires 7d (also 30m, 12h, 2w, or a date), droppage update <slug> file.html --expires 7d|never, or droppage expire <slug> <when|never> without re-uploading. An expired page shows "This page has expired." (HTTP 410) to everyone, including the owner, and its images stop working; a daily cleanup deletes the page and its images for good. droppage list gained an EXPIRES column and list --json rows gained expires_at (null means never). Nothing expires unless set.
    • A view is one unique visitor per page. Refreshes, reopening in the same browser, link previews from chat apps, and the owner's own opens no longer add views. The monthly view quota counts each visitor once per page per month. Existing totals are not recalculated. Bandwidth is still measured per delivery.
    • Signed-in owners open their own private, email, and password pages without the email link or password. Every gate shows a sign-in link. No action needed.
  12. Compatible update

    Account plans can be changed in place

    Paid accounts can move between Starter and Builder or switch monthly and yearly billing without opening a duplicate subscription.

    • Account usage and plan status are visible at droppage.dev/account.
    • Existing links remain live when a plan changes or a usage limit is reached.
    • The CLI reports quota state in machine-readable JSON.
  13. Compatible update

    Email-protected reports gained recipient management

    Publishers can add, resend, inspect, and remove approved recipients while delivery runs safely in the background.

    • Email allowlists are available on the Builder plan.
    • Invitation retries are idempotent and visible to the publisher.
GET /updates.json

Stable schema version 1 · current CLI 0.5.1 · no per-command polling.

Know when droppage gets better.

One short dispatch when a useful release ships or the workflow changes. Every note is on this page too, with or without subscribing.

Confirm by email. Occasional product updates. Unsubscribe anytime.