- Upgrade Vite from ^8.2.2 to ^8.3.5 in both package-lock.json and package.json.
- Update @oxc-project/types version from 0.147.0 to 0.155.0 in package-lock.json.
- Change funding URL for @oxc-project/types in package-lock.json.
- Upgrade multiple @rolldown/binding packages from version 1.2.6 to 1.2.15 in package-lock.json.
* feat: Keyboard Submit and Escape for Tool Approval Cards
The reject reason and response fields submit by the composer's Enter
rules, the JSON edit field submits on Ctrl/Cmd+Enter only, and a submit
shortcut rebound off Enter works in all three. Escape in the composer
review panel collapses it and returns focus to its toggle, as does the
Collapse button. The no-host binding default moves into
useComposerBindings so the ask and approval cards share it.
* test: Cover Tool Approval Keyboard Control in E2E Scenarios
* fix: Match the Composer Submit Chord in the Approval JSON Field and Guard Safari IME Escape
* fix: Mirror Page Components For RTL Layouts
* fix: Keep the Project Workspace Panel Group LTR Under RTL
The workspace reversed its panels under RTL but left the group inheriting the document direction, so the flex row reversed them again: details stayed on the left and the separator dragged backwards. Add RTL scenarios for the project workspace, shared artifacts pane and marketplace category tabs.
* fix: Drop the Conflicting RTL Margins on the Agent Detail Close Button
The logical -me-2 already pulls the button to the inline end, so the leftover rtl: overrides pushed it into the header under RTL.
* test: Drag RTL Separators in Pointer-Sized Steps
* fix: Keep Input Adornments on the Side Their Field Reserves
* fix: Remount the Project Workspace Separator When Direction Changes
* test: Cover RTL Separator Keys and the Prompt Counter
* fix: Remount the Shared Artifacts Separator When Direction Changes
* test: Open the Prompt Counter Scenario From the Create Dialog
* test: Allow Sub-Pixel Rounding Beside the Prompt Counter
* fix: Inset the Prompt Name From Its Inline Start
* test: Open the Scrim Spec's Row Menu by Focus
The row's menu button mounts on row hover or focus. When this spec shares a
worker with specs that leave a streaming chat in the sidebar, the list
remounts rows under the pointer and the hover never mounts the button. The
leak is pre-existing and tracked separately; this spec now focuses the row it
seeded and repeats the focus until the menu button holds it.
* refactor: Move the Resumable Generation Start Into the Chat Core
* fix: Call a Host Transport's Start on the Transport Itself
Forwarding transport.start as a bare function rebound this to the resumable host, breaking any host transport whose start is an instance method.
* test: Cover Interface and Chat Direction Scenarios
* test: Pin the Default Textarea Direction to Auto
* refactor: Keep the Chat Direction Preference in Jotai
* test: Drive Direction Scenarios Through Phone Settings and a Held Bundle
* fix: Mirror Shared Primitives For RTL Layouts
* fix: Import the Direction Helper Relatively in InfoHoverCard
* test: Cover Mirrored Switch and Dialog Close in RTL
* fix: Keep the Focused Sign-In Label Inside Its Field in RTL
* fix: Mirror by Element Direction and Re-Resolve Side Placement on Open
* test: Pin RTL Scenarios to the Element Direction and Expect a Trailing Number Input
* fix: Keep Time Column Arrow Keys Vertical in RTL
* fix: Keep :dir() Selectors Through CSS Minification
* chore: Declare lightningcss for the Client Build Config
* fix: Keep SelectDropDown Left and Right Icon Sides Physical
* fix: Fall Back to the dir Attribute Where :dir() Is Unsupported
* fix: Leave Nested LTR Islands Unmirrored in the dir Attribute Fallback
* fix: Resolve the Slider Direction From Its Nearest dir
* fix: Resolve the Nearest dir at Any Depth in the :dir() Fallback
* fix: Re-Resolve the Slider Direction When a dir Attribute Changes
* fix: Keep the Provider Direction for a Slider Without a dir Ancestor
* fix: Read an Automatic dir From the Computed Direction for the Slider
* fix: Prefer the Computed Direction When Resolving an Element's Direction
* fix: Re-Resolve the Slider Under a dir=auto Boundary When Its Content Changes
* fix: Keep the Mirrored Combobox Placement Across Rerenders
* refactor: Let the Slider Read Its Direction From the Radix Provider
* fix: Space a Trailing Combobox Option Icon From Its Label
* fix: Mirror Chat Surfaces For RTL Layouts
* fix: Keep Short Subagent Ticker Lines at Their Reading Start
Adds RTL chat scenarios covering code, markdown blocks, sibling arrows and virtualized lists.
* fix: Resolve Quote and List Direction From Their Content
dir=auto skips descendants that carry their own dir, so a quote or loose list holding dir=auto paragraphs always resolved left-to-right. Lists now take one direction so markers and indent stay on the same side.
* fix: Keep Tables, Callouts and Trace Axes on One Direction
Tables take one direction from their content so cell borders share a frame; strong-direction detection skips Arabic-Indic digits, separators and marks; handoff and answer callouts use a logical start border; trace tick and range labels stay on the LTR axis.
* fix: Treat Every Script's Letters as Strong Direction
Direction detection now keys on Unicode letters, so Devanagari, Thai and other LTR scripts resolve LTR. E2E specs that selected rows by pl-6 now select ps-6.
* test: Cover the Shared Strong Direction Helper on Its Own
* fix: Read Bidi Marks and Native Script Digits as Strong Direction
* fix: Approximate Bidi Classes by Block So Symbols and Numerals Resolve
* fix: Resolve Strong Direction From Unicode Bidi Class Tables
* docs: Note How the Bidi Tables Are Generated and Where They Differ
* fix: Generate the Bidi Tables From Unicode 17 Including L-Class Marks
* fix: Anchor Sidebar, Drawer and Panels to the Inline Edges in RTL
* test: Cover the Mirrored Shell in RTL with Scenario Specs
* test: Wait for the Sidebar Width Transition Before Dragging
* test: Cover a Live Switch to RTL With the Artifacts Panel Open
* fix: Follow the Interface Direction in Radix, the Composer and First Paint
Wrap the app in a Radix DirectionProvider driven by i18n so Tabs, Select and
menus stop rendering LTR subtrees in right-to-left locales, and swipe toasts
toward the inline end.
Chat direction becomes auto, ltr or rtl (auto by default; stored LTR/RTL
values are kept). The composer applies a forced direction as a dir attribute
instead of reversing rows, which double-flipped under an RTL document, and the
text fields default to dir=auto. The unused Jotai chat direction atom that
pinned every TextareaAutosize to ltr is removed.
index.html sets dir before first paint, and the language setting no longer
races i18n over document.lang.
* fix: Keep the Empty Composer Placeholder on the Interface's Reading Edge
A tool call that is the only one in its group, inside a phase of several, renders its panel bare: open, with no row of its own. The full-content request only fired when the reader expanded the card, so a bare panel stayed on the server preview, showing truncated output and keeping its copy buttons disabled. Bash, generic and the other useToolCallState cards now request the stored part whenever they render bare.
* refactor: Draw Provider Icons as Theme-Following Brand Marks
Replace the raster and oversized provider art with single colour SVG marks
that inherit currentColor. Marks come from simple-icons (CC0) or are cut
from the logo each brand publishes, as noted per entry in marks.ts.
Lemonade, MLX, ShuttleAI and Unify keep their raster art for now.
The Cohere landing padding only compensated for the old PNG, so it goes.
* fix: Use the Groq Wordmark G Instead of the Site Favicon Bolt
* ⌨️ feat: Keyboard submit for ask_user_question answer box
The interactive ask_user_question card's answer textarea had no key
handling, so the answer could only be submitted by clicking. Route its
keydown through resolveComposerKeyDown so it follows the composer's
Enter-to-send preference, a rebound submit chord, and IME composition.
The run is paused rather than generating, so it resolves as idle and
Ctrl/Cmd+Enter submits instead of reaching the during-run actions.
* ⌨️ feat: Keyboard focus and confirm for batched ask_user_question
- Focus the first question's controls when a batch arrives, only when
focus is idle (body, or the empty composer that sent the turn), and
focus into the next step on advance instead of the fieldset: the picked
or first option, else the answer field.
- Enter on the already-picked single-select option confirms the step;
Enter on an unpicked option stays its click, so a pick never submits
by itself (WCAG 3.2.2). Multi-select rows only toggle.
- Ctrl/Cmd+Enter confirm from the answer field like Enter; Shift+Enter
never does.
* 🐛 fix: Keep Held Enter and Remounts From Picking Batched Answers
Review findings on the batched ask_user_question card, and what this
commit does about each.
1. Held or double-tapped Enter could pick answers and submit the batch.
After Enter confirmed a step, focus moved to the next step's first
option. A keyboard Enter on a focused button is its click, so the
key repeat of a held Enter (or a quick double-tap) picked that option
and advanced again. On the last step the next repeat landed on the
now-pressed option, confirmed it, and submitted the whole batch with
answers the user never chose.
Fix: after a step change, focus goes to the step's picked option,
else its answer field. An unpicked option is only a focus target when
a batch first arrives. Repeats now reach a text field, which can page
on but never picks an option or submits on the user's behalf.
2. Focus-on-arrival ran on every mount, not only on arrival. Its effect
has empty deps, so moving the batch between the composer popover and
the chat card, or remounting a message that still holds an
unanswered batch (reopening a conversation, a Share view), pulled
focus onto an option of that batch. The next Enter or Space would
then answer it.
Fix: `AskUserQuestions` takes a `focusOnArrival` prop, set only by
the surface showing the live pause (the popover, or the chat card
while it is live and visible), so other mounts never take focus.
Focus is placed at most once per batch, tracked by action id, so a
move between surfaces is not treated as a new arrival.
Tests: a held Enter from an answer field picks nothing and never
submits; a surface that isn't the live pause leaves focus alone; a
remount of the same batch doesn't take focus again. All three fail
without this change. The Chat/Messages/Content, Chat/Input, Chat/ask
and hooks/Input suites pass, apart from TokenUsage/index.spec.tsx,
which fails the same way without this change. tsc, ESLint and Prettier
are clean on the changed files.
* feat: Escape to Skip Ask Cards and Move the Popover to Chat
Escape in the chat card skips the question or batch, but only before
anything is entered, so a stray Escape cannot discard an answer and
resume the run. Escape with focus inside the composer popover moves the
question to the chat, as it already did from the composer, and returns
focus to the composer once the popover closes. Also drops the em dashes
from the batched card's comments.
* fix: Read Enter-to-Send From the Chat Surface Host in the Ask Card
* test: Cover Ask Batch Keyboard Control in E2E Scenarios
* fix: Keep Held and Modified Enter From Submitting Ask Answers
Ignore auto-repeated Enter before confirming a picked option, so a held
Enter cannot both pick and submit the last question. In the answer
field, Shift, Alt and repeated Enter now prevent the enclosing chat
form's implicit submit instead of returning early. Escape that cancels
an IME composition no longer moves the popover to the chat, and the
arrival-focus flag lives in the batch's Jotai form state.
* fix: Honor a Submit Shortcut Rebound Off Enter in Ask Answer Fields
The window shortcut handler yields submitMessage in every editing field
except the composer, so a chord such as Ctrl+J did nothing in the ask
answer fields. Both the single-question answer box and the batched
answer field now act on it, through a shared isReboundSubmitChord.
---------
Co-authored-by: elie605 <ebtien@gmail.com>
* fix: Hold the Locked Composer to One Line Under a Batch Question
A batch ask_user_question card sits above the composer with its own 70vh cap, while a multi-line draft kept the disabled textarea at 45 to 55vh. Together they could exceed the viewport and push the prompt and the move-to-chat control off screen. The composer now takes its collapsed one-line height while the batch owns it, and the collapse toggle stands down since it cannot expand a locked composer.
* test: Cover the Batch Card Above a Long Composer Draft
* fix: Wait for Chat History Before URL Auto-Submit
Existing chats refuse a send until their message history has loaded and
settled, so a ?q=...&submit=true link on a slow-loading chat consumed its
one auto-submit attempt on a refusal and left the prompt unsent. Hold the
submission in its preparing state and retry when the history query
resolves, giving up only if the history request fails.
* test: Cover URL Auto-Submit on a Slow-Loading Chat
* fix: Retry URL Auto-Submit After the History Render
A query cache listener fired while the history was being written, before
the composer re-rendered, so the send derived no latest message and forked
from the root. Observe the messages query instead and retry from an effect,
which runs after the render that carries the loaded history.
* fix: Pair English Plural Keys as _one/_other for Locize
Locize groups keys by plural suffix and generates every form a language
needs. Families that paired a bare base key with _one surfaced empty-source
_other rows, and literal keys ending in _other or _one spawned unrelated
plural siblings. Rename the bases to _other, rename the colliding literal
keys, and guard the English file against a regression.
* test: Cover Plural Version Count and Other Issue Feedback Tag
* fix: Announce a Single Running or Finished Chat in the Singular
* fix: Resolve Plural Forms From Base Keys So Locale Plural Rules Apply
Selecting an explicit _other key bypassed i18next's plural resolution, so a
single running chat was announced in the plural and locale forms such as
_zero and _many were never chosen. Call sites pass the base key with a
numeric count again, and TranslationKeys accepts plural base keys.
* fix: Let i18next Pick Duration Plural Forms From a Numeric Count
Duration and elapsed announcements selected an explicit _one or _other key
and passed the formatted number as count, so locale forms such as _few and
_many were unreachable. They now pass the base key with a numeric count and
interpolate the locale-formatted number as value.
* fix: Route Subagent Files Delivered After a Mid-Run Reload
* test: Stub Stored Part Queries in the ContentParts Integration Suite
* fix: Recover Stored Part Lookups That Fail Without a Reader
* fix: Resolve Late Subagent Files With One Previewed Message Read
* fix: Read Late Subagent Hints Again Until the File Is Saved
* fix: Count Failed Reads Toward the Late Hint Poll Bound
* fix: Let Unresolved Late Hint Reads Recover on Focus and Reconnect
* fix: Resolve Late Subagent File Owners From the Stored Transcripts
* fix: Ask for Late Subagent File Owners in Bounded Batches
* fix: Render Files Saved by Tools Inside a Subagent Run
* test: Cover Subagent Nested Tool Images After Reload
* fix: Hoist Subagent Child-Run Files With Grouped Tool Calls
* fix: Route Live Subagent Child Files Through the Part Attachment Map
* fix: Keep Subagent Child File Routing Through Previews and Ownership Rules
* test: Match Subagent Image Names Exactly
* fix: Key Subagent Child Files by Their Owning Part
* fix: Apply Attachment Scope Rules to Subagent Child Calls
* fix: Carry Child Call Scope Through Previews and Live Progress
* fix: Retain Live Subagent Progress Readers and Seen Child Calls
* fix: Keep Live Progress Keys Retained Across Streamed Deltas
* fix: Assign Subagent Child Files Once Per Message
* fix: Route Late and Id-less Subagent Child Files
* fix: Keep Seen Subagent Child Calls With Their Invocation
* fix: Use Streamed Index and Call-Level Owner for Subagent Child Files
* fix: Reserve Scoped Child Files From Unscoped Top-Level Calls
* fix: Record Subagent Child Calls When Progress Is Written
* fix: Keep Agent Scope on Remembered Subagent Child Calls
* refactor: Share One Subagent Child Call Collector
* fix: Derive Live Signature From Remembered Child Calls
* fix: Keep Child Calls a Bounded Batch Evicts
* fix: Bound Remembered Subagent Child Calls and Include Replay Segments
* fix: Refresh Owners of Shown Files in the Bounded Call History
* fix: Keep Remembered Call Order Stable Across Eviction Replays
* fix: Scope Preview Hints to Attachments and Walk Nested Calls Iteratively
* fix: Bound Wildcard Preview Hints and Own Live Calls by Their Run
* fix: Own Stored Subagent Child Calls by Their Persisted Identity
happy-dom 20 holds each MutationObserver callback only through a WeakRef, so a garbage collection between two mutations silently unregisters the hook's observer and the removal is never delivered. Under load that GC lands mid-test and the spec reads data-active="true" after the attribute is gone. jsdom keeps registered observers alive the way browsers do.
* feat: open durable subagents from background tasks
* fix: isolate subagent focus and discovery from navigation
* fix: retain subagent task identity through navigation
* test: verify task opening without changing the rendered popup
* fix: preserve retained task activity across navigation
* fix: import the core progress key after dev integration
* fix: refresh subagent panel return focus on explicit open
* fix: prefer the subagent panel opener when restoring focus
* test: retain the actual reply stamp across permission grant
* test: scope permission-grant notifications to the target reply
* test: observe the pending reply before granting notification permission
---------
Co-authored-by: Lia <lia@librechat.ai>