Versions, backups and drafts

New versions

• "Upload new version" on the drop page replaces the code at the same link. The version number goes up by one (v1, v2, v3 and so on).
• Name, description, password, visibility and stored data stay as they are. Data saved by visitors is not part of a version.

The version list

• Clicking the version line at the top of the drop page ("v3 · updated …") opens the Versions panel: every version of the drop, newest first, with the date, who made it ("Uploaded by you", "Update from your AI", "Restored from version 2", "Adjusted by Toolcrow"), what the AI wrote about an update, and how many reports it solved.
• Toolcrow keeps the code of the latest versions, the live one included. How many depends on the plan; the panel says the number. Older versions stay in the list as "Code not kept". Versions from before the list existed (November 2026) show that line too. When a plan keeps fewer versions (for example after a downgrade), the code of the older ones is removed within a day, without waiting for a new version.
• View and Restore are on every version whose code is kept. View opens that version in a new tab, as a private link for the maker that is valid for a short time; nothing changes. Restore makes it the live version again (see "Restoring" below).
• The bar at the top of the maker's own view of a tool shows the same list under the version number, with a link to the Versions panel.
• Delete code: the maker can delete the saved code of any version except the live one, for example when it held a key or personal data that was removed later. The code is removed everywhere Toolcrow kept it, including the backup if it is that version. The version stays in the list as "Code deleted by you". To remove something from the live version, upload a new version first.

The backup and restoring

• The previous version is the backup.
• "Restore" on any kept version makes it the live version again. The current version becomes the backup, so a restore can itself be undone, and the restored code is saved as a new version with a new number ("Restored from version 2"). Restoring the backup swaps the two.
• Viewing and restoring older versions is not possible for a drop that Toolcrow took down, or for an account that can no longer publish (the maker can email hello@toolcrow.app).
• A restore reopens feedback whose fix was in a version it rolls back: the report is open again in Nest with the line "Reopened: the fix in v5 was rolled back", and the drop page says how many reports were reopened. Reports marked as fixed by hand (not linked to a version) stay closed. Restoring the version with the fix again does not close them by itself; the maker marks them as fixed.

Downloading the code

• The code of a drop belongs to its maker. "Download code" in the Versions panel (under the live version) downloads the code of the live version, so the maker can keep a copy or run the tool somewhere else.
• What comes out: a single HTML file stays one .html file. A React component, a Vue component or plain JavaScript comes as a .zip with the code as it was uploaded (source.jsx, source.vue or source.js) and index.html, the page Toolcrow made of it, which opens in a browser as it is. A drop made of several files (an uploaded website, a PDF) comes as a .zip with all its files and folders.
• It is the maker's own code: what Toolcrow adds around a drop while serving it (the "Powered by Toolcrow" badge, the feedback button, sharing and the storage helpers) is not in the download. A change in the code itself, such as a published update or an automatic adjustment after deploy (see Building and importing), is in it, because that is the live version.
• Only the owner of a drop can download its code; anyone else gets a refusal. A drop that Toolcrow took down cannot be downloaded (the maker can email hello@toolcrow.app).
• Data that visitors saved is not part of the code. It is exported separately on the Submissions page, as CSV or JSON (see Saving data).
• Outside Toolcrow, what the code gets from Toolcrow stops working: Tooldrop.opslaan(), shared window.storage, Tooldrop.context and AI calls through Toolcrow (see Saving data and AI inside a drop). Everything else runs as it does in a browser; a tool that only saves on the visitor's own device keeps doing so.

Drafts (updates) from the maker's AI or from Toolcrow

• With an AI connected to Toolcrow (see Connecting your own AI), the AI can prepare an improved version of a drop as a draft. A draft is never live by itself.
• Toolcrow can also prepare a draft itself, for example when a tool loses its data on refresh. The side panel then says "Update from Toolcrow" instead of "Update from your AI".
• When the draft came from an AI app connected by signing in, the drop page names that app: "ChatGPT prepared an update" and "Update from ChatGPT" (or Claude, or Claude Code). The name comes from where that connection sends the maker back after signing in, not from what the AI says about itself. A draft from the personal link says "your AI", because Toolcrow does not know which app uses that link.
• Each drop has at most one open draft. A new proposal from the maker's AI replaces it (also a draft from Toolcrow; the AI's response then says so), or the AI builds on it in rounds; the drop page shows how many rounds the AI has made. Toolcrow never replaces a draft from the maker's AI.
• On the drop page the maker sees "Update ready" and a Check update button. It opens a side panel that shows what changed and why (the code changes stay folded away until asked for), and the maker can open "Try it" (a private test link that is valid for a short time), and then chooses Publish or Discard. While the maker's AI is reading the tool's feedback or code, the drop page says "Your AI is working on an update", and the update appears there by itself, without reloading. There is no email for a draft from their AI: the maker asked for it, and it also shows in Nest.
• "Try it" runs the draft the way the live tool runs: shared window.storage, Tooldrop.opslaan(), Tooldrop.context and AI calls through Toolcrow all work (see Saving data and AI inside a drop). That means the draft uses the real data of the live tool. What the maker saves while trying a draft is saved for real, shows up for everyone and is forwarded like any other submission (see Saving data). A notice at the top of the draft says so. Only the maker can open this test link; the badge, the feedback button and What's new are not shown there, and opening it does not count as a visit.
• Publish turns the draft into the next version, with the current version kept as the backup. If the live version changed after the draft was made, publishing is refused, so nothing is overwritten by accident.

Closing feedback with a new version

• A draft can be linked to the feedback items it fixes. The side panel lists them under "Fixes these N reports", each with a checkbox that is on by default. When building on a draft in rounds, the links of earlier rounds are kept.
• Publish marks only the checked items as done, with the version that fixed them, and confirms how many it closed ("3 reports closed in v5"). Unchecked items stay open. Discarding a draft leaves all its items open.
• "Upload new version" asks "Does this version fix any open reports?" with the same checkboxes, off by default, so feedback can also be closed without a connected AI.
• In Nest an open report that is linked to a waiting draft shows "Fix ready", and its next step becomes "Check update", which opens the drop page with the draft. A fixed report shows the date of the version it was fixed in. A draft that is not linked to any open report is its own item in Nest ("Update").
• A draft can change at most 20 files, each up to 10 MB.

Telling visitors what changed

• Each new version can carry one short note for the people who use the drop, shown under "What's new" in the drop (see Feedback and Nest). The field "Note for people who use this drop" is in the update side panel and in "Upload new version". Empty means no note.
• The maker's AI can suggest the note when it prepares a draft (whats_new, one sentence in the language of the drop, no code or internal details); the maker sees it in the field and can change it before publishing.
• A restore hides the notes of the versions it rolls back, and shows the note of the restored version again.