diff --git a/.changeset/design-attachments.md b/.changeset/design-attachments.md
deleted file mode 100644
index fedd7240fd79..000000000000
--- a/.changeset/design-attachments.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@reddb-io/redcode": minor
-"@reddb-io/redcode-core": minor
----
-
-Design mode: real image attachments, a self-paint check, and Tailwind, DaisyUI and Mermaid shipped for prototypes
-
-Images attached to a note — from the composer or from the card on an element — are uploaded to a content-addressed store under the data directory (owner-only files, magic bytes decide the type, PNG/JPEG/WebP only), and reach the agent as files on disk. Limits are configurable under `experimental.design.attachments`: 10 MiB per image, 4 per note, 25 MiB per note, a 7-day TTL and a 512 MiB quota swept hourly without ever touching an image a turn may still be reading. A send whose images cannot be honoured is refused whole, and the page says which cap was hit. `design_preview` adds a note when a page never paints its own surface, since text styled for an assumed dark or light host can be invisible. Prototypes have no network, so redcode now serves Tailwind's browser runtime, DaisyUI (with its themes) and Mermaid at `/design/vendor/`, and the prompt states the design-direction rule: what the user asked for, then the project's own design system, then these.
diff --git a/.changeset/design-export.md b/.changeset/design-export.md
deleted file mode 100644
index 0cc6c564b20d..000000000000
--- a/.changeset/design-export.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@reddb-io/redcode": minor
-"@reddb-io/redcode-core": minor
----
-
-Design mode: a self-contained export, and the review from another device
-
-`design_export` (and ⋮ → Export standalone HTML on the review page) writes the prototype as one HTML file with its own stylesheets, classic scripts, images, fonts and media inlined, along with the Tailwind, DaisyUI and Mermaid redcode serves, so it opens from disk or anywhere with no redcode running. Remote references are left for the browser; nothing is fetched, and every local read is confined to the prototype directory by real path, so a symlink cannot carry an outside file into a page that may be shared. What could not be inlined is listed for the agent and counted for the person. The transform is lavish-axi's export bundler, vendored whole with its tests. Caps under `experimental.design.export` (10 MB per asset, 25 MB per export). When the server listens beyond loopback, `design_preview` prints the URL a phone on the same network can open and the page offers it under ⋮; the review surface now answers only under names that are this machine (loopback, the bound hostname, its addresses and its own name, plus `experimental.design.hosts`), so a page elsewhere that resolves its name here cannot drive it.
diff --git a/.changeset/design-layout-audit.md b/.changeset/design-layout-audit.md
deleted file mode 100644
index bbfb1ff160a3..000000000000
--- a/.changeset/design-layout-audit.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@reddb-io/redcode": minor
-"@reddb-io/redcode-core": minor
----
-
-Design mode: a passive layout audit with an inbox the person triages
-
-The prototype now audits its own layout after fonts, geometry and finite animations settle: text clipped by its container, controls cut off or outside the viewport, text off-screen, a page that scrolls sideways, text covered by an opaque sibling. Findings survive only if two samples agree, and every pass reports its own completeness. They land in a "Layout issues" inbox on the review page — badge, drawer, select, queue, dismiss, reveal — and nothing in it reaches the agent until the person queues it, when it becomes one ordinary note. A warning is cleared only by a complete pass on a newer revision that no longer finds it; a failed pass, a different viewport or a reload in flight never clears anything, and a dismissal lasts one revision. Every frame load is named by a token so a pass from a replaced frame is discarded. The page holds the prototype behind a short curtain until its first pass (`experimental.design.gate`, `gate_timeout`, or `?gate=0` for one tab), asks the server whether the document can be served when the frame stays silent, and the one report that does wake the agent unasked is a prototype that cannot be shown at all (`<artifact-failures>`). Viewport classes can be narrowed with `experimental.design.viewports`; a class left out has its warnings marked obsolete rather than resolved.
diff --git a/.changeset/design-playbooks.md b/.changeset/design-playbooks.md
deleted file mode 100644
index e567c8e9035c..000000000000
--- a/.changeset/design-playbooks.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@reddb-io/redcode": minor
----
-
-Design mode: playbooks on demand
-
-A new `design_playbook` tool hands the agent lavish's seven playbooks — diagram, table, comparison, plan, code, input (collecting answers inside the page), slides — rewritten for redcode's review page and a prototype that has no network. The mode's prompt carries the router (open every playbook that matches before writing HTML) and the playbook itself is read on the turn that needs it, so the prompt stays short.
diff --git a/.changeset/design-review.md b/.changeset/design-review.md
deleted file mode 100644
index 079774972ec7..000000000000
--- a/.changeset/design-review.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@reddb-io/redcode": minor
----
-
-Design mode: the conversation, live reload, ending the review, and a sheet on the phone
-
-The review page is now a conversation: what you send and what the agent replies, queued notes as pills, Send to Agent, Hold, and Send & End; a menu with the prototype's path, reload, a DOM snapshot copy, and End review. A change on disk reloads the prototype while someone is looking, and the page keeps the person's place, their unsent card text, and answers inside `data-redcode-question` across that reload — a note whose element disappears for two revisions is handed back as text, never lost. Everything a person wrote survives a reload of the page itself. The server streams reloads, the agent's replies and presence over `/design/:id/events`; who ended the review is remembered, a person's end is not reopened by the agent unless asked (`design_preview` gains `reopen`), and `design_exit` ends the review as the agent. The review's state lives in a sidecar beside the prototype and an index in the data directory, so a restarted server still knows an open tab. Below 860px the panel becomes a sheet raised from a dock.
diff --git a/.changeset/design-sdk.md b/.changeset/design-sdk.md
deleted file mode 100644
index 8f7b3fb56585..000000000000
--- a/.changeset/design-sdk.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@reddb-io/redcode": minor
----
-
-Design mode reviews like lavish: annotate or explore, text ranges, table cells, Mermaid nodes
-
-The review client is now the lavish-axi loop, natively. Annotate mode is on by default (Cmd/Ctrl+I toggles explore; alt-click still annotates there); native controls keep working. A note can anchor to a text selection (with range anchors), a table cell (named by its visible row and column when that is provable), or a Mermaid node (by the diagram's own ids), and the agent reads each as such. Artifacts get `window.redcodeDesign` (`window.lavish` as an alias) with `queuePrompt`, `sendQueuedPrompts`, `endSession`, `setStatus`, `snapshot`, and `data-redcode-action` / `data-redcode-question` (lavish's names accepted too); an unsent answer for the same control replaces the earlier one. A send carries a bounded DOM snapshot after the notes, and can end the review. The shell replays scroll position and an unsent card draft after the prototype reloads, and adopts the prototype's title and icon.
diff --git a/.changeset/design-whiteboard.md b/.changeset/design-whiteboard.md
deleted file mode 100644
index 3233d7551068..000000000000
--- a/.changeset/design-whiteboard.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@reddb-io/redcode": minor
----
-
-Design mode: Mermaid diagrams open as whiteboards
-
-Every rendered diagram in a `.mermaid` (or `data-redcode-mermaid`) container gets an Excalidraw whiteboard beside it, and a Fullscreen action that opens the same one over the page: converted from the Mermaid source, drawn on and rearranged, autosaved beside the review's own state, and queued as one ordinary note carrying a summary of what changed (added, removed, moved, relabeled, drawn) plus the edited scene and a PNG preview on disk. The agent edits the Mermaid source in response; nothing is ever converted back. A scene saved for an older version of a diagram is never merged silently: the person chooses between re-converting and keeping their edits. The frames run sandboxed with no origin and no server access; the review page does every read and write, and only for a frame that proved a channel token minted for this prototype and its descent from the prototype frame. The bundle (Excalidraw, the converter with its exactly pinned Mermaid, React) is not in the binary: a release ships it as `redcode-whiteboard-<version>.tar.gz`, fetched into the data directory the first time a review needs it (`REDCODE_DISABLE_WHITEBOARD_DOWNLOAD=1` to never fetch, `REDCODE_WHITEBOARD_DIR` to point at a build); a source checkout builds it with `bun run build:whiteboard`. Until it is there, diagrams stay as they are.
diff --git a/package.json b/package.json
index eee8d256cac7..99728a4598e1 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@reddb-io/redcode-workspace",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "description": "RedDB's AI-powered development tool",
   "private": true,
   "type": "module",
diff --git a/packages/app/CHANGELOG.md b/packages/app/CHANGELOG.md
index 2038cd62d04d..858e678cd5c7 100644
--- a/packages/app/CHANGELOG.md
+++ b/packages/app/CHANGELOG.md
@@ -1,5 +1,15 @@
 # @reddb-io/redcode-app
 
+## 1.21.1
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+  - @reddb-io/redcode-session-ui@1.18.25
+
 ## 1.21.0
 
 ### Minor Changes
diff --git a/packages/app/package.json b/packages/app/package.json
index 8250f6bf3a1e..4d4cc415d583 100644
--- a/packages/app/package.json
+++ b/packages/app/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reddb-io/redcode-app",
-  "version": "1.21.0",
+  "version": "1.21.1",
   "description": "",
   "type": "module",
   "exports": {
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index 1a6211b25e20..ea86eaddde51 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,16 @@
 # @reddb-io/redcode-cli
 
+## 1.18.25
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+  - @reddb-io/redcode-server@1.18.25
+  - @reddb-io/redcode-tui@1.21.1
+
 ## 1.18.24
 
 ### Patch Changes
diff --git a/packages/cli/package.json b/packages/cli/package.json
index a8b13ff8522f..c592da8c1279 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@reddb-io/redcode-cli",
-  "version": "1.18.24",
+  "version": "1.18.25",
   "type": "module",
   "license": "MIT",
   "bin": {
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
index 9d07f521572a..f2cfddbe1c57 100644
--- a/packages/core/CHANGELOG.md
+++ b/packages/core/CHANGELOG.md
@@ -1,5 +1,21 @@
 # @reddb-io/redcode-core
 
+## 1.22.0
+
+### Minor Changes
+
+- fce66aa: Design mode: real image attachments, a self-paint check, and Tailwind, DaisyUI and Mermaid shipped for prototypes
+
+  Images attached to a note — from the composer or from the card on an element — are uploaded to a content-addressed store under the data directory (owner-only files, magic bytes decide the type, PNG/JPEG/WebP only), and reach the agent as files on disk. Limits are configurable under `experimental.design.attachments`: 10 MiB per image, 4 per note, 25 MiB per note, a 7-day TTL and a 512 MiB quota swept hourly without ever touching an image a turn may still be reading. A send whose images cannot be honoured is refused whole, and the page says which cap was hit. `design_preview` adds a note when a page never paints its own surface, since text styled for an assumed dark or light host can be invisible. Prototypes have no network, so redcode now serves Tailwind's browser runtime, DaisyUI (with its themes) and Mermaid at `/design/vendor/`, and the prompt states the design-direction rule: what the user asked for, then the project's own design system, then these.
+
+- 8993328: Design mode: a self-contained export, and the review from another device
+
+  `design_export` (and ⋮ → Export standalone HTML on the review page) writes the prototype as one HTML file with its own stylesheets, classic scripts, images, fonts and media inlined, along with the Tailwind, DaisyUI and Mermaid redcode serves, so it opens from disk or anywhere with no redcode running. Remote references are left for the browser; nothing is fetched, and every local read is confined to the prototype directory by real path, so a symlink cannot carry an outside file into a page that may be shared. What could not be inlined is listed for the agent and counted for the person. The transform is lavish-axi's export bundler, vendored whole with its tests. Caps under `experimental.design.export` (10 MB per asset, 25 MB per export). When the server listens beyond loopback, `design_preview` prints the URL a phone on the same network can open and the page offers it under ⋮; the review surface now answers only under names that are this machine (loopback, the bound hostname, its addresses and its own name, plus `experimental.design.hosts`), so a page elsewhere that resolves its name here cannot drive it.
+
+- 6e2e844: Design mode: a passive layout audit with an inbox the person triages
+
+  The prototype now audits its own layout after fonts, geometry and finite animations settle: text clipped by its container, controls cut off or outside the viewport, text off-screen, a page that scrolls sideways, text covered by an opaque sibling. Findings survive only if two samples agree, and every pass reports its own completeness. They land in a "Layout issues" inbox on the review page — badge, drawer, select, queue, dismiss, reveal — and nothing in it reaches the agent until the person queues it, when it becomes one ordinary note. A warning is cleared only by a complete pass on a newer revision that no longer finds it; a failed pass, a different viewport or a reload in flight never clears anything, and a dismissal lasts one revision. Every frame load is named by a token so a pass from a replaced frame is discarded. The page holds the prototype behind a short curtain until its first pass (`experimental.design.gate`, `gate_timeout`, or `?gate=0` for one tab), asks the server whether the document can be served when the frame stays silent, and the one report that does wake the agent unasked is a prototype that cannot be shown at all (`<artifact-failures>`). Viewport classes can be narrowed with `experimental.design.viewports`; a class left out has its warnings marked obsolete rather than resolved.
+
 ## 1.21.1
 
 ### Patch Changes
diff --git a/packages/core/package.json b/packages/core/package.json
index b3cfc7afb0c2..f26792f683be 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
-  "version": "1.21.1",
+  "version": "1.22.0",
   "name": "@reddb-io/redcode-core",
   "type": "module",
   "license": "MIT",
diff --git a/packages/enterprise/CHANGELOG.md b/packages/enterprise/CHANGELOG.md
index 232161b3d754..cfb568f9d107 100644
--- a/packages/enterprise/CHANGELOG.md
+++ b/packages/enterprise/CHANGELOG.md
@@ -1,5 +1,15 @@
 # @reddb-io/redcode-enterprise
 
+## 1.18.25
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+  - @reddb-io/redcode-session-ui@1.18.25
+
 ## 1.18.24
 
 ### Patch Changes
diff --git a/packages/enterprise/package.json b/packages/enterprise/package.json
index e6a3b2d11b78..66d2bcab51a2 100644
--- a/packages/enterprise/package.json
+++ b/packages/enterprise/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reddb-io/redcode-enterprise",
-  "version": "1.18.24",
+  "version": "1.18.25",
   "private": true,
   "type": "module",
   "license": "MIT",
diff --git a/packages/redcode/CHANGELOG.md b/packages/redcode/CHANGELOG.md
index 0383c900b37c..d3e4b853ec94 100644
--- a/packages/redcode/CHANGELOG.md
+++ b/packages/redcode/CHANGELOG.md
@@ -1,5 +1,42 @@
 # opencode
 
+## 0.20.0
+
+### Minor Changes
+
+- fce66aa: Design mode: real image attachments, a self-paint check, and Tailwind, DaisyUI and Mermaid shipped for prototypes
+
+  Images attached to a note — from the composer or from the card on an element — are uploaded to a content-addressed store under the data directory (owner-only files, magic bytes decide the type, PNG/JPEG/WebP only), and reach the agent as files on disk. Limits are configurable under `experimental.design.attachments`: 10 MiB per image, 4 per note, 25 MiB per note, a 7-day TTL and a 512 MiB quota swept hourly without ever touching an image a turn may still be reading. A send whose images cannot be honoured is refused whole, and the page says which cap was hit. `design_preview` adds a note when a page never paints its own surface, since text styled for an assumed dark or light host can be invisible. Prototypes have no network, so redcode now serves Tailwind's browser runtime, DaisyUI (with its themes) and Mermaid at `/design/vendor/`, and the prompt states the design-direction rule: what the user asked for, then the project's own design system, then these.
+
+- 8993328: Design mode: a self-contained export, and the review from another device
+
+  `design_export` (and ⋮ → Export standalone HTML on the review page) writes the prototype as one HTML file with its own stylesheets, classic scripts, images, fonts and media inlined, along with the Tailwind, DaisyUI and Mermaid redcode serves, so it opens from disk or anywhere with no redcode running. Remote references are left for the browser; nothing is fetched, and every local read is confined to the prototype directory by real path, so a symlink cannot carry an outside file into a page that may be shared. What could not be inlined is listed for the agent and counted for the person. The transform is lavish-axi's export bundler, vendored whole with its tests. Caps under `experimental.design.export` (10 MB per asset, 25 MB per export). When the server listens beyond loopback, `design_preview` prints the URL a phone on the same network can open and the page offers it under ⋮; the review surface now answers only under names that are this machine (loopback, the bound hostname, its addresses and its own name, plus `experimental.design.hosts`), so a page elsewhere that resolves its name here cannot drive it.
+
+- 6e2e844: Design mode: a passive layout audit with an inbox the person triages
+
+  The prototype now audits its own layout after fonts, geometry and finite animations settle: text clipped by its container, controls cut off or outside the viewport, text off-screen, a page that scrolls sideways, text covered by an opaque sibling. Findings survive only if two samples agree, and every pass reports its own completeness. They land in a "Layout issues" inbox on the review page — badge, drawer, select, queue, dismiss, reveal — and nothing in it reaches the agent until the person queues it, when it becomes one ordinary note. A warning is cleared only by a complete pass on a newer revision that no longer finds it; a failed pass, a different viewport or a reload in flight never clears anything, and a dismissal lasts one revision. Every frame load is named by a token so a pass from a replaced frame is discarded. The page holds the prototype behind a short curtain until its first pass (`experimental.design.gate`, `gate_timeout`, or `?gate=0` for one tab), asks the server whether the document can be served when the frame stays silent, and the one report that does wake the agent unasked is a prototype that cannot be shown at all (`<artifact-failures>`). Viewport classes can be narrowed with `experimental.design.viewports`; a class left out has its warnings marked obsolete rather than resolved.
+
+- 448242c: Design mode: playbooks on demand
+
+  A new `design_playbook` tool hands the agent lavish's seven playbooks — diagram, table, comparison, plan, code, input (collecting answers inside the page), slides — rewritten for redcode's review page and a prototype that has no network. The mode's prompt carries the router (open every playbook that matches before writing HTML) and the playbook itself is read on the turn that needs it, so the prompt stays short.
+
+- 89356bb: Design mode: the conversation, live reload, ending the review, and a sheet on the phone
+
+  The review page is now a conversation: what you send and what the agent replies, queued notes as pills, Send to Agent, Hold, and Send & End; a menu with the prototype's path, reload, a DOM snapshot copy, and End review. A change on disk reloads the prototype while someone is looking, and the page keeps the person's place, their unsent card text, and answers inside `data-redcode-question` across that reload — a note whose element disappears for two revisions is handed back as text, never lost. Everything a person wrote survives a reload of the page itself. The server streams reloads, the agent's replies and presence over `/design/:id/events`; who ended the review is remembered, a person's end is not reopened by the agent unless asked (`design_preview` gains `reopen`), and `design_exit` ends the review as the agent. The review's state lives in a sidecar beside the prototype and an index in the data directory, so a restarted server still knows an open tab. Below 860px the panel becomes a sheet raised from a dock.
+
+- c7509de: Design mode reviews like lavish: annotate or explore, text ranges, table cells, Mermaid nodes
+
+  The review client is now the lavish-axi loop, natively. Annotate mode is on by default (Cmd/Ctrl+I toggles explore; alt-click still annotates there); native controls keep working. A note can anchor to a text selection (with range anchors), a table cell (named by its visible row and column when that is provable), or a Mermaid node (by the diagram's own ids), and the agent reads each as such. Artifacts get `window.redcodeDesign` (`window.lavish` as an alias) with `queuePrompt`, `sendQueuedPrompts`, `endSession`, `setStatus`, `snapshot`, and `data-redcode-action` / `data-redcode-question` (lavish's names accepted too); an unsent answer for the same control replaces the earlier one. A send carries a bounded DOM snapshot after the notes, and can end the review. The shell replays scroll position and an unsent card draft after the prototype reloads, and adopts the prototype's title and icon.
+
+- 3a6f023: Design mode: Mermaid diagrams open as whiteboards
+
+  Every rendered diagram in a `.mermaid` (or `data-redcode-mermaid`) container gets an Excalidraw whiteboard beside it, and a Fullscreen action that opens the same one over the page: converted from the Mermaid source, drawn on and rearranged, autosaved beside the review's own state, and queued as one ordinary note carrying a summary of what changed (added, removed, moved, relabeled, drawn) plus the edited scene and a PNG preview on disk. The agent edits the Mermaid source in response; nothing is ever converted back. A scene saved for an older version of a diagram is never merged silently: the person chooses between re-converting and keeping their edits. The frames run sandboxed with no origin and no server access; the review page does every read and write, and only for a frame that proved a channel token minted for this prototype and its descent from the prototype frame. The bundle (Excalidraw, the converter with its exactly pinned Mermaid, React) is not in the binary: a release ships it as `redcode-whiteboard-<version>.tar.gz`, fetched into the data directory the first time a review needs it (`REDCODE_DISABLE_WHITEBOARD_DOWNLOAD=1` to never fetch, `REDCODE_WHITEBOARD_DIR` to point at a build); a source checkout builds it with `bun run build:whiteboard`. Until it is there, diagrams stay as they are.
+
+### Patch Changes
+
+- @reddb-io/redcode-server@1.18.25
+- @reddb-io/redcode-tui@1.21.1
+
 ## 0.19.0
 
 ### Minor Changes
diff --git a/packages/redcode/package.json b/packages/redcode/package.json
index 11efdcdfa1b1..b9b5d46a2141 100644
--- a/packages/redcode/package.json
+++ b/packages/redcode/package.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "name": "@reddb-io/redcode",
   "type": "module",
   "license": "MIT",
diff --git a/packages/sdk-next/CHANGELOG.md b/packages/sdk-next/CHANGELOG.md
index e2d907026371..e4c2b7f1fdf2 100644
--- a/packages/sdk-next/CHANGELOG.md
+++ b/packages/sdk-next/CHANGELOG.md
@@ -1,5 +1,16 @@
 # @reddb-io/redcode-sdk-next
 
+## 1.18.25
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+  - @reddb-io/redcode-client@1.18.21
+  - @reddb-io/redcode-server@1.18.25
+
 ## 1.18.24
 
 ### Patch Changes
diff --git a/packages/sdk-next/package.json b/packages/sdk-next/package.json
index 544441300409..916f80f95e97 100644
--- a/packages/sdk-next/package.json
+++ b/packages/sdk-next/package.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@reddb-io/redcode-sdk-next",
-  "version": "1.18.24",
+  "version": "1.18.25",
   "private": true,
   "type": "module",
   "license": "MIT",
diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md
index f9658078ed54..c93de0a81e6f 100644
--- a/packages/server/CHANGELOG.md
+++ b/packages/server/CHANGELOG.md
@@ -1,5 +1,14 @@
 # @reddb-io/redcode-server
 
+## 1.18.25
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+
 ## 1.18.24
 
 ### Patch Changes
diff --git a/packages/server/package.json b/packages/server/package.json
index 22648f484ccb..340ebdae6b66 100644
--- a/packages/server/package.json
+++ b/packages/server/package.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@reddb-io/redcode-server",
-  "version": "1.18.24",
+  "version": "1.18.25",
   "private": true,
   "type": "module",
   "license": "MIT",
diff --git a/packages/session-ui/CHANGELOG.md b/packages/session-ui/CHANGELOG.md
index af7a2126ce9c..45d808aee0aa 100644
--- a/packages/session-ui/CHANGELOG.md
+++ b/packages/session-ui/CHANGELOG.md
@@ -1,5 +1,14 @@
 # @reddb-io/redcode-session-ui
 
+## 1.18.25
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+
 ## 1.18.24
 
 ### Patch Changes
diff --git a/packages/session-ui/package.json b/packages/session-ui/package.json
index 4036e0b6b328..60e38569588a 100644
--- a/packages/session-ui/package.json
+++ b/packages/session-ui/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@reddb-io/redcode-session-ui",
-  "version": "1.18.24",
+  "version": "1.18.25",
   "private": true,
   "type": "module",
   "license": "MIT",
diff --git a/packages/tui/CHANGELOG.md b/packages/tui/CHANGELOG.md
index 9eaf272c215f..9b7e2978600e 100644
--- a/packages/tui/CHANGELOG.md
+++ b/packages/tui/CHANGELOG.md
@@ -1,5 +1,14 @@
 # @reddb-io/redcode-tui
 
+## 1.21.1
+
+### Patch Changes
+
+- Updated dependencies [fce66aa]
+- Updated dependencies [8993328]
+- Updated dependencies [6e2e844]
+  - @reddb-io/redcode-core@1.22.0
+
 ## 1.21.0
 
 ### Minor Changes
diff --git a/packages/tui/package.json b/packages/tui/package.json
index 4151c618e69d..1742baac6346 100644
--- a/packages/tui/package.json
+++ b/packages/tui/package.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@reddb-io/redcode-tui",
-  "version": "1.21.0",
+  "version": "1.21.1",
   "private": true,
   "type": "module",
   "license": "MIT",