rhashcode
diff --git a/‎.agents/skills/address-feedback/SKILL.md‎
Lines changed: 112 additions & 0 deletions b/‎.agents/skills/address-feedback/SKILL.md‎
Lines changed: 112 additions & 0 deletions
diff --git a/‎.changeset/core-assistant-chat-empty-bubble.md‎
Lines changed: 5 additions & 0 deletions b/‎.changeset/core-assistant-chat-empty-bubble.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎.changeset/core-composer-inline-images-attachments.md‎
Lines changed: 5 additions & 0 deletions b/‎.changeset/core-composer-inline-images-attachments.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎.changeset/core-sync-per-key-app-state.md‎
Lines changed: 5 additions & 0 deletions b/‎.changeset/core-sync-per-key-app-state.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎.changeset/core-voice-cancel-during-transcribe.md‎
Lines changed: 5 additions & 0 deletions b/‎.changeset/core-voice-cancel-during-transcribe.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions b/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎packages/core/src/client/AssistantChat.display.spec.ts‎
Lines changed: 14 additions & 0 deletions b/‎packages/core/src/client/AssistantChat.display.spec.ts‎
Lines changed: 14 additions & 0 deletions
diff --git a/‎packages/core/src/client/AssistantChat.tsx‎
Lines changed: 52 additions & 38 deletions b/‎packages/core/src/client/AssistantChat.tsx‎
Lines changed: 52 additions & 38 deletions
diff --git a/‎packages/core/src/client/composer/PromptComposer.spec.ts‎
Lines changed: 30 additions & 0 deletions b/‎packages/core/src/client/composer/PromptComposer.spec.ts‎
Lines changed: 30 additions & 0 deletions
@@ -0,0 +1,112 @@
+---
+name: address-feedback
+description: >-
+  Triage feedback docs or pasted feedback into bugs to fix, UX suggestions to
+  propose, unclear questions, and skipped noise; verify bugs, check Sentry when
+  relevant, and keep UI changes minimal.
+---
+
+# Address Feedback
+
+Use this skill when the user shares a feedback document, issue, thread, or pasted notes and asks you to address the feedback.
+
+The default posture is judgment plus action: fix clear, verified bugs you agree with; propose UX changes with rationale; skip or flag low-signal, unclear, or out-of-scope items.
+
+## Prerequisites
+
+- If no link or feedback text is provided, ask for it.
+- Read the repo `AGENTS.md` before touching code.
+- Use the relevant connector/plugin/skill for the source when available, instead of scraping authenticated pages.
+
+## Steps
+
+1. Read the feedback source.
+
+   | Source | Reader |
+   | --- | --- |
+   | Notion link | Notion connector or Notion skill |
+   | Google Docs/Drive link | Google Drive connector or Google Docs skill |
+   | Linear link | Linear connector if installed; otherwise ask for pasted content |
+   | GitHub issue or PR | GitHub connector or `gh issue view` / `gh pr view` |
+   | Slack thread | Slack connector |
+   | Public URL | Web browsing |
+   | Pasted text | Read directly |
+
+   Use web browsing only for public URLs. Auth-gated docs usually need their matching connector.
+
+2. Categorize every actionable item.
+
+   - **Bug**: Broken behavior, crash, wrong data, dead link, package/API mismatch, or captured exception. Verify and fix when you agree.
+   - **UX suggestion**: Design, discoverability, workflow, or feature feedback. Propose the cleanest version first unless the user explicitly asked you to implement UX changes.
+   - **Question or unclear**: Missing detail, contradictory feedback, or behavior you cannot inspect. Ask or flag it.
+   - **Out of scope**: Outside this repo, already shipped, intentionally unsupported, or too low-signal. Note briefly and skip.
+
+3. Check Sentry when the feedback smells like an error.
+
+   - Use the Sentry skill/plugin if available, or the repo's Sentry scripts if documented.
+   - Search by route, stack symbol, error text, and symptom keywords.
+   - Default org is `builder-io` unless the user specifies another.
+   - Cite issue IDs or links when you find a match.
+   - If nothing matches, say that plainly.
+
+4. Fix only the clear bugs you agree with.
+
+   - Verify before fixing: reproduce locally, read the relevant code, inspect logs, or confirm with a stack trace.
+   - Keep each fix narrow and mapped to a feedback item.
+   - Follow existing project conventions and nearby patterns.
+   - Do not switch branches, stash, reset, force-push, or open a PR unless the user asks.
+   - Add or update focused tests when the bug risk warrants it.
+
+5. Treat UX feedback with restraint.
+
+   Do not solve UX problems by adding more visible controls, helper text, banners, top-level nav, or always-open panels by default. Prefer cleaner interaction models:
+
+   - Make the existing primary action more discoverable.
+   - Remove competing elements so the right action stands out.
+   - Move secondary actions into `DropdownMenu`, `Popover`, `Sheet`, `Collapsible`, or tabs.
+   - Improve empty states around one clear action.
+   - Use progressive disclosure for optional or advanced controls.
+
+   When proposing a UX change, write it as: what to change, why it helps, and the tradeoff. Keep each proposal short.
+
+6. Verify changed behavior.
+
+   - Run the smallest relevant test or typecheck command.
+   - For UI fixes, verify in a browser when feasible and inspect the actual screen.
+   - If you cannot run a useful verification, say why.
+
+## Report Format
+
+Keep the final report short:
+
+```md
+## Bugs Fixed
+- [feedback item] - [what changed, file:line]
+
+## Bugs Flagged But Not Fixed
+- [feedback item] - [why]
+
+## UX Suggestions
+- [feedback item] -> [proposed change]
+
+## Skipped
+- [feedback item] - [reason]
+```
+
+Only include sections that have content. The user can read the diff; do not write a second feedback document.
+
+## Avoid
+
+- Do not agree with every suggestion by default.
+- Do not bundle unrelated cleanups.
+- Do not implement UX changes that make an important screen busier without explicit user approval.
+- Do not claim a UI change is done without browser verification when a local app can be run.
+- Do not invent Sentry matches, affected users, or reproduction steps.
+
+## Related Skills
+
+- `github:gh-address-comments` for GitHub PR review threads.
+- `github:gh-fix-ci` for failing GitHub checks.
+- `sentry:sentry` for production error investigation.
+- `frontend-design` for approved UI implementation work.
+- `qa` for broader browser verification.
@@ -0,0 +1,5 @@
+---
+"@agent-native/core": patch
+---
+
+`AssistantChat`: hide the empty user-message bubble when the text content is nothing but an injected `<context>...</context>` block. Previously, sending an attachment-only composer-mode message (e.g. `/code` with a file but no prose) rendered an empty grey bubble in the chat after the context tags were stripped. The message now skips the bubble + expand/collapse UI entirely when the only attachment is context; attachment chips still render above.
@@ -0,0 +1,5 @@
+---
+"@agent-native/core": minor
+---
+
+`PromptComposer` + `TiptapComposer`: inline image attachments, attachment-only composer-mode sends, and active-voice cancellation on submit. Image files attached to the composer are now sent inline as `<uploaded-image name=… contentType=…>` data-URL blocks alongside the existing pasted-text / inline-text flattening. Composer modes (`/code`, `/research`, etc.) now also accept submissions with no text when attachments are present — the default prompt becomes "Use the attached context." and the attachments survive the wrap in the mode's prefix + `<context>` block. Every send / build intercept path also cancels any in-flight voice dictation so a late transcript can't land on top of the just-sent message.
@@ -0,0 +1,5 @@
+---
+"@agent-native/core": patch
+---
+
+`useDbSync` + server poll: per-key invalidation for application_state one-shot commands. The poll loop now emits one event per changed (key, owner) pair instead of a single `key: "*"` wildcard, and the client only invalidates `navigate-command` / `show-questions` / `__set_url__` queries when those specific keys actually change. Noisy app-state keys (template-specific UI state, per-tab flags) no longer wake the navigation / question readers on every poll cycle.
@@ -0,0 +1,5 @@
+---
+"@agent-native/core": patch
+---
+
+`useVoiceDictation`: cancelling while the transcription request is in flight now actually drops the response. Previously `cancel()` returned early for any state other than `recording` / `starting`, so once the network POST started, a cancel click was a no-op and the transcribed text would still be inserted into the composer after the user cancelled. The fetch handlers (both success and live-snapshot fallback) now check `cancelledRef` immediately after the await and bail without forwarding.
@@ -70,6 +70,7 @@ Agent skills in `.agents/skills/` provide detailed guidance. Read the relevant s
 
 | Skill                  | When to use                                                   |
 | ---------------------- | ------------------------------------------------------------- |
+| `address-feedback`     | Triage feedback docs into bugs to fix and UX proposals        |
 | `adding-a-feature`     | Adding any new feature (the four-area checklist)              |
 | `actions`              | Creating or running agent actions                             |
 | `storing-data`         | Adding data models, reading/writing config or state           |
 
@@ -0,0 +1,14 @@
+// @vitest-environment happy-dom
+
+import { describe, expect, it } from "vitest";
+import { displayableUserMessageText } from "./AssistantChat.js";
+
+describe("displayableUserMessageText", () => {
+  it("treats context-only messages as empty for user bubble display", () => {
+    expect(
+      displayableUserMessageText(
+        "\n\n<context>\nHidden attachment instructions\n</context>",
+      ),
+    ).toBe("");
+  });
+});
@@ -1713,9 +1713,7 @@ const plainMentionPattern = /((?:^|(?<=\s))@(\w+))/g;
 
 function UserMessageText({ text }: { text: string }) {
   // Strip injected <context>...</context> blocks before display
-  const displayText = text
-    .replace(/<context>[\s\S]*?<\/context>\n?/g, "")
-    .trim();
+  const displayText = displayableUserMessageText(text);
 
   const parts: React.ReactNode[] = [];
   let lastIndex = 0;
@@ -1779,6 +1777,10 @@ function UserMessageText({ text }: { text: string }) {
   return <>{parts.length > 0 ? parts : displayText}</>;
 }
 
+export function displayableUserMessageText(text: string): string {
+  return text.replace(/<context>[\s\S]*?<\/context>\n?/g, "").trim();
+}
+
 function UserMessageAttachments() {
   const messageRuntime = useMessageRuntime();
   const msg = messageRuntime.getState();
@@ -1837,11 +1839,19 @@ function UserMessage() {
   const [isExpandable, setIsExpandable] = useState(false);
   const contentRef = useRef<HTMLDivElement>(null);
   const messageRuntime = useMessageRuntime();
-  const timestamp = formatMessageTimestamp(messageRuntime.getState().createdAt);
+  const message = messageRuntime.getState();
+  const timestamp = formatMessageTimestamp(message.createdAt);
+  const hasDisplayableText =
+    message.content
+      ?.filter((part): part is { type: "text"; text: string } => {
+        return part.type === "text" && typeof part.text === "string";
+      })
+      .some((part) => displayableUserMessageText(part.text).length > 0) ??
+    false;
 
   useEffect(() => {
     const el = contentRef.current;
-    if (!el) return;
+    if (!el || !hasDisplayableText) return;
 
     const measure = () => {
       setIsExpandable(el.scrollHeight > 200);
@@ -1851,7 +1861,7 @@ function UserMessage() {
     const observer = new ResizeObserver(measure);
     observer.observe(el);
     return () => observer.disconnect();
-  }, []);
+  }, [hasDisplayableText]);
 
   return (
     <div
@@ -1860,41 +1870,45 @@ function UserMessage() {
     >
       <div className="max-w-[85%]">
         <UserMessageAttachments />
-        <div
-          className="relative rounded-lg bg-accent px-3 py-2 text-sm leading-relaxed text-foreground"
-          onCopy={(e) => {
-            const selection = window.getSelection();
-            if (!selection || selection.rangeCount === 0) return;
-            const fragment = selection.getRangeAt(0).cloneContents();
-            const mentions = fragment.querySelectorAll("[data-mention-label]");
-            if (mentions.length === 0) return;
-            e.preventDefault();
-            mentions.forEach((el) => {
-              el.textContent = `@${el.getAttribute("data-mention-label")}`;
-            });
-            const div = document.createElement("div");
-            div.appendChild(fragment);
-            e.clipboardData.setData("text/plain", div.textContent || "");
-          }}
-        >
+        {hasDisplayableText && (
           <div
-            ref={contentRef}
-            className={cn(
-              "whitespace-pre-wrap break-words",
-              !expanded && isExpandable && "max-h-[200px] overflow-hidden",
-            )}
+            className="relative rounded-lg bg-accent px-3 py-2 text-sm leading-relaxed text-foreground"
+            onCopy={(e) => {
+              const selection = window.getSelection();
+              if (!selection || selection.rangeCount === 0) return;
+              const fragment = selection.getRangeAt(0).cloneContents();
+              const mentions = fragment.querySelectorAll(
+                "[data-mention-label]",
+              );
+              if (mentions.length === 0) return;
+              e.preventDefault();
+              mentions.forEach((el) => {
+                el.textContent = `@${el.getAttribute("data-mention-label")}`;
+              });
+              const div = document.createElement("div");
+              div.appendChild(fragment);
+              e.clipboardData.setData("text/plain", div.textContent || "");
+            }}
           >
-            <MessagePrimitive.Parts
-              components={{
-                Text: UserMessageText,
-              }}
-            />
+            <div
+              ref={contentRef}
+              className={cn(
+                "whitespace-pre-wrap break-words",
+                !expanded && isExpandable && "max-h-[200px] overflow-hidden",
+              )}
+            >
+              <MessagePrimitive.Parts
+                components={{
+                  Text: UserMessageText,
+                }}
+              />
+            </div>
+            {!expanded && isExpandable && (
+              <div className="pointer-events-none absolute inset-x-0 bottom-0 h-14 rounded-b-lg bg-gradient-to-t from-accent via-accent/90 to-transparent" />
+            )}
           </div>
-          {!expanded && isExpandable && (
-            <div className="pointer-events-none absolute inset-x-0 bottom-0 h-14 rounded-b-lg bg-gradient-to-t from-accent via-accent/90 to-transparent" />
-          )}
-        </div>
-        {isExpandable && (
+        )}
+        {hasDisplayableText && isExpandable && (
           <button
             type="button"
             onClick={() => setExpanded((prev) => !prev)}
 
@@ -0,0 +1,30 @@
+// @vitest-environment happy-dom
+
+import { describe, expect, it } from "vitest";
+import { buildPromptComposerSubmission } from "./PromptComposer.js";
+
+describe("buildPromptComposerSubmission", () => {
+  it("inlines image-only submissions so standalone flows receive a prompt", async () => {
+    const file = new File(["fake image"], "sketch.png", {
+      type: "image/png",
+    });
+
+    const result = await buildPromptComposerSubmission({
+      text: "",
+      attachments: [
+        {
+          id: "sketch.png",
+          name: "sketch.png",
+          type: "image",
+          file,
+        },
+      ],
+    });
+
+    expect(result.files).toEqual([file]);
+    expect(result.text).toContain(
+      '<uploaded-image name="sketch.png" contentType="image/png">',
+    );
+    expect(result.text).toContain("data:image/png;base64,");
+  });
+});
-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +---
 +"@agent-native/core": patch
 +---
++
 +`AssistantChat`: hide the empty user-message bubble when the text content is nothing but an injected `<context>...</context>` block. Previously, sending an attachment-only composer-mode message (e.g. `/code` with a file but no prose) rendered an empty grey bubble in the chat after the context tags were stripped. The message now skips the bubble + expand/collapse UI entirely when the only attachment is context; attachment chips still render above.