@mindstudio-ai/remy 0.1.222 → 0.1.224

package/dist/headless.d.ts

@@ -131,7 +131,14 @@ declare class HeadlessSession {
      * `state.models`. Omitting `models` (or sending an empty object) resets
      * every agent to "use server defaults". */
     private handleChangeModels;
-    /** Cancel the running turn and drain the queue. Returns the drained items. */
+    /**
+     * Cancel the running turn and flush the follow-ups that belonged to it
+     * (`chain`/`background`), while preserving `source: 'user'` items — those are
+     * independent user intent, not tied to the aborted run. The preserved user
+     * messages run next: `runSingleTurn` swallows the abort, so `handleMessage`
+     * falls through to `drainQueueLoop` with `running` still held. Returns the
+     * flushed items (for the cancel command's resume/discard UX).
+     */
     private handleCancel;
     /**
      * Remove pending queued messages — all user messages, or one by id.

package/dist/headless.js

@@ -8180,7 +8180,14 @@ var HeadlessSession = class {
       allowedModelsByType: ALLOWED_MODELS_BY_TYPE
     };
   }
-  /** Cancel the running turn and drain the queue. Returns the drained items. */
+  /**
+   * Cancel the running turn and flush the follow-ups that belonged to it
+   * (`chain`/`background`), while preserving `source: 'user'` items — those are
+   * independent user intent, not tied to the aborted run. The preserved user
+   * messages run next: `runSingleTurn` swallows the abort, so `handleMessage`
+   * falls through to `drainQueueLoop` with `running` still held. Returns the
+   * flushed items (for the cancel command's resume/discard UX).
+   */
   handleCancel() {
     if (this.currentAbort) {
       this.currentAbort.abort();
@@ -8190,7 +8197,7 @@ var HeadlessSession = class {
       pending.resolve(USER_CANCELLED_RESULT);
       this.pendingTools.delete(id);
     }
-    return this.queue.drain();
+    return this.queue.removeWhere((item) => item.source !== "user");
   }
   /**
    * Remove pending queued messages — all user messages, or one by id.

package/dist/index.js

@@ -9019,7 +9019,14 @@ var init_headless = __esm({
           allowedModelsByType: ALLOWED_MODELS_BY_TYPE
         };
       }
-      /** Cancel the running turn and drain the queue. Returns the drained items. */
+      /**
+       * Cancel the running turn and flush the follow-ups that belonged to it
+       * (`chain`/`background`), while preserving `source: 'user'` items — those are
+       * independent user intent, not tied to the aborted run. The preserved user
+       * messages run next: `runSingleTurn` swallows the abort, so `handleMessage`
+       * falls through to `drainQueueLoop` with `running` still held. Returns the
+       * flushed items (for the cancel command's resume/discard UX).
+       */
       handleCancel() {
         if (this.currentAbort) {
           this.currentAbort.abort();
@@ -9029,7 +9036,7 @@ var init_headless = __esm({
           pending.resolve(USER_CANCELLED_RESULT);
           this.pendingTools.delete(id);
         }
-        return this.queue.drain();
+        return this.queue.removeWhere((item) => item.source !== "user");
       }
       /**
        * Remove pending queued messages — all user messages, or one by id.

package/dist/prompt/compiled/design.md

@@ -102,7 +102,7 @@ Always rely on the details provided by the design expert - their work is the sou
 
 - **Avoid generic fonts.** Avoid overused defaults that strip away all personality.
 - **Avoid AI-default palettes.** Two clusters dominate current AI-tool homepages and instinct will pull you toward them: purple/indigo gradients (the "AI purple" problem) and warm editorial palettes of cream/parchment backgrounds with burnt-orange/rust/terracotta accents (the "AI homepage" look). When you find yourself reaching for either family, deliberately pick something else — ask whether the palette could be on the homepage of a current AI startup, and if yes, route around it.
-- **Avoid colored border callout boxes.** Avoid rounded divs with a thick colored `border-left|top` — the generic "info card" pattern. Instead: use typography, spacing, and background tints to create hierarchy. If you need to call something out, use a full subtle background or a top border.
+- **Never put a single-side colored border on a rounded element.** Never add a colored accent border to one side — or any subset of sides — of a rounded div, card, or callout. This bans `border-left`, `border-right`, `border-top`, and `border-bottom` accents, individually and in every combination — there is no acceptable side and no exceptions. This is the generic AI "info card" slop. To call something out, use a full subtle background tint (never an edge accent), typography, and spacing.
 - **Avoid three equal boxes with icons.** The default AI landing page layout. Instead: use asymmetric layouts, varied column widths, or a single focused content area. Avoid cards labelled things like: 1, 2, 3 - this feels generic and cheap.
 - **Avoid "1,2,3" boxes on landing pages** Never use sections with numerical labels to describe a high level flow on a landing page.
 - **Avoid timid color palettes.** Avoid evenly distributed, non-committal colors. Commit to a direction and be bold.

package/dist/subagents/designExpert/prompts/components.md

@@ -44,4 +44,4 @@ Forms should feel like interactions, not paperwork.
 
 ### Outdated Component Patterns to Avoid
 
-- Avoid rounded cards with a single side colored border (e.g., border-radius + a blue border-left for a draggable card) as it looks dated and generic. Consider different ways to make cards appear stateful - like icons, shadows, and colors.
+- Never make a rounded card look stateful, selected, or draggable with a colored border on one side — or any subset of sides. No `border-left`, `border-right`, `border-top`, or `border-bottom` accent, in any combination — there are no exceptions. This "rounded card + single-side colored border" look is dated, generic slop. Show state with icons, background-tint shifts, elevation/shadow, or the content's own color.

package/dist/subagents/designExpert/prompts/frontend-design-notes.md

@@ -47,7 +47,7 @@ Every interface must work on both desktop and mobile.
 
 - **Avoid generic fonts.** Overused defaults that strip away all personality. Instead: pick a distinctive Google Font that fits the app's character.
 - **Avoid AI-default palettes.** Two clusters dominate current AI-tool homepages and instinct will pull you toward them: purple/indigo gradients (the "AI purple" problem) and warm editorial palettes of cream/parchment backgrounds with burnt-orange/rust/terracotta accents (the "AI homepage" look). When you find yourself reaching for either family, deliberately pick something else — ask whether the palette could be on the homepage of a current AI startup, and if yes, route around it. Challenge yourself to choose beautiful, modern, 2026-inspired colors that don't fit either mold.
-- **Avoid colored left-border callout boxes.** Rounded divs with a thick colored `border-left` — the generic "info card" pattern. Instead: use typography, spacing, and background tints to create hierarchy. If you need to call something out, use a full subtle background or a top border.
+- **Never put a single-side colored border on a rounded element.** Never add a colored accent border to one side — or any subset of sides — of a rounded div, card, or callout. This bans `border-left`, `border-right`, `border-top`, and `border-bottom` accents, individually and in every combination — there is no acceptable side and no exceptions. This is the generic AI "info card" slop. To call something out, use a full subtle background tint (never an edge accent), typography, and spacing.
 - **Avoid three equal boxes with icons.** The default AI landing page layout. Instead: use asymmetric layouts, varied column widths, or a single focused content area.
 - **Avoid timid color palettes.** Evenly distributed, non-committal colors. Instead: one or two dominant colors with sharp accents. Commit to a direction.
 - **Avoid card-heavy nested layouts.** Cards inside cards, everything boxed. Instead: use space, typography, and dividers to create hierarchy without extra containers.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.222",
+  "version": "0.1.224",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",