The menu panel, tooltip and tab trigger read menuRadius, tooltipRadius and tabRadius instead of literal corners. The defaults are the old literals, and the ClickHouse theme sets Click UI's genericMenu, tooltip and tabs radii. The not-expressible list drops the three corners and keeps the field fill and ink, the dark menu shadow and the tooltip shadow.
* refactor: Start and Stream Agent Turns Through the Chat Transport
useResumableSSE now POSTs the turn with transport.start and attaches with
transport.stream({ token }).reconnectToStream, both read from ChatTransportContext.
The new transport spec renders the hook with a fake transport and covers the started
and rejected start.
* refactor: Stream Assistants Turns Through the Chat Transport
useSSE sends the turn with transport.stream({ token }).send from ChatTransportContext.
The transport spec covers the request it makes, closing on unmount, and a stream error.
* refactor: Stop Generations Through the Chat Transport
useAbortStreamMutation takes its mutation from transport.abort, and the Assistants
abort request moves from a fetch in useEventHandlers to transport.abortRun. The transport
spec stops an agents run and an Assistants run against a fake transport, including a
rejected stop.
* refactor: Steer Running Generations Through the Chat Transport
The steer, cancel-steer and arm-steer mutation hooks take their requests from
transport.steer, transport.cancelSteer and transport.armSteer. The transport spec
steers a running generation against a fake transport and checks that a refused steer
is kept as a queued turn.
* refactor: Queue Turns Through the Chat Transport
The queued-turn projection reads through transport.listQueued, and the enqueue and
cancel mutation hooks take transport.enqueue and transport.cancelQueued. The transport
spec reads, adds and withdraws a server queued turn against a fake transport, and keeps a
turn local when the server has no queue. The steer tests now answer the projection from
the fake transport instead of the request layer.
* test: Type the Transport Spec's Recoil Seeds
The seed callbacks take recoil's MutableSnapshot instead of a type read off RecoilRoot's
props union, which has no initializeState member on every branch. Drops the unused emit
helper.
* test: Cover Steer Cancel and Arm at the Transport Boundary
useSteerReclaim withdraws a waiting steer through transport.cancelSteer and
useSteerEscalate arms one through transport.armSteer, each against the fake transport.
The host-supplied surface (app-global chat settings and the wire turns run over) is now
typed in hooks/Chat/contract.ts. ChatSettingsContext takes its types from there, and a new
ChatTransportContext carries a Transport whose default wraps the existing SSE transport and
generation request functions. The host route supplies both. Nothing reads the transport yet.
The disabled-fill and field-focus variants, and the Field.css edge rules, read the inherited --theme-disabled-style and --theme-field-focus-style properties through style queries instead of matching any ancestor that carries the data-theme-* marker. A root themed with the default style inside one themed with the other now gets its own behavior back, at any depth. The default treatment never depends on style query support.
* feat: Focus ring width and offset theme roles
The global keyboard focus outline and the keyboard-modality text input outline read focusRingWidth and focusRingOffset instead of 2px literals. Both default to 2px, the ClickHouse theme sets Click UI's 2px and 2px, and the drift guard pins those values against Click UI's focus rules.
* test: Complete the Click UI not-expressible list
The parity spec now probes the Dropdown menu shadow, the Tooltip corner and shadow and the Tabs corner. The menu shadow reads the shadowLg role, whose default is the old literal, so ClickHouse matches Click UI in light; the dark app rule, the Tooltip literals and the Tabs corner have no role and are listed with their issues.
* test: Pin the menu panel shadow in the default and ClickHouse themes
The global keyboard focus outline and the keyboard-modality text input outline read focusRingWidth and focusRingOffset instead of 2px literals. Both default to 2px, the ClickHouse theme sets Click UI's 2px and 2px, and the drift guard pins those values against Click UI's focus rules.
* feat: Give the Badge Label Its Own Ink and Let the Legacy Dialog Spinner Inherit
The shared Badge inherited the primary ink, so a theme could not label it
in Click UI's muted badge ink without dimming body copy. It now reads a
badge-label color role that defaults to the primary ink and follows it for
a theme that names only that; a hovered or selected badge keeps the primary
ink, which holds AA on those fills. The ClickHouse theme takes Click UI's
badge.opaque.color.text.default, and the Badge label leaves the drift
guard's not-expressible list.
The template's legacy selection spinner painted in text-primary on the
primary fill, dark on dark. It now takes the action's own foreground.
* refactor: Fold the Avatar Glyph Into the Shared Primary Ink Fallback
The default avatar's glyph, the dialog title and the badge label all split
out of the primary ink and follow it for a theme that names only that, so
the avatar keeps one fallback with the others instead of its own copy in
resolveTheme and applyTheme.
* fix: Keep a Disabled Badge in Its Resting Ink on Hover
* fix: Keep a Disabled Selected Badge in the Primary Ink on Hover
* feat: add ephemeral retention mode for forced temporary chats
Adds RetentionMode.EPHEMERAL, which forces every newly saved chat
temporary: hidden from history and search, given the temporary-chat
expiration, and with the toggle locked on.
Forces isTemporary and applies the temporary expiration in the normal
conversation and message save methods, routes Assistants/Threads
messages through the normal message save, applies the all-data
retention policy to file uploads and shared links, and stamps imports,
forks, and duplicates. Locks the frontend toggle and keyboard shortcut
behind an administrator-enforced badge.
The default temporary mode and the existing all mode are unchanged.
* fix: enforce ephemeral retention when resuming paused chats
* fix: preserve forced retention across pauses and assistant turns
* test: Use Real Module IDs for Installed Package Mocks
* test: Wait for Resumed Retention Persistence
* test: Control Mongo Index Setup in OpenID Fixture
* test: Close Mobile Drawer Before Retention Resume Scenario
* fix: Store Responses API Messages Under the Retention Write Context
Input and output messages were saved with the raw request, so under
ephemeral retention they missed the forced-temporary classification the
conversation received. Route both through getConversationWriteContext
and announce the stored reply as saved.
* fix: Align Resumed Responses With the Parent Retention Deadline
A resumed response was saved with a fresh forced-temporary window while
the re-stamp kept the conversation's earlier deadline, so a chat that
paused again could leave its response stored after the conversation
expired. Stamp the saved response with the parent's deadline.
* fix: Clear Released Bookmark Tags When Forcing a Chat Temporary
stampForcedRetention released a converted chat's bookmark counts but
kept its tags, so deleting that chat before TTL removal decremented the
same tags again and reduced counts owned by other visible chats. Clear
the tags in the conditional conversion update that releases them.
* fix: Store No Bookmark Tags on Forced-Temporary Imports
An ephemeral import, fork or duplicate skipped its tag count increment
but kept the source tags, so deleting the copy before TTL removal
decremented counts owned by other visible chats. Store the same tags the
import counts, which is none for a forced-temporary copy.
* test: Provide the Forced-Temporary Retention Helper to the Header Stacking Mock
* test: Reuse One Admin Login per Worker in Ephemeral Retention Scenarios
* fix: Keep Legacy Temporary Chats Temporary When Forking Under All-Data Retention
* fix: Convert a Resumed Chat Under Ephemeral Retention Before It Can Re-Pause Empty
* fix: Treat a Reloaded Pre-Policy Run as Temporary Once Retention Is Forced
* fix: Stamp Messages with the Deadline a Concurrent Retention Stamp Stored
* fix: Wait for the Startup Config Before Rebuilding a Resumed Submission
* test: Wait for the Resumed Response Row in the Ephemeral Resume Scenario
* test: Provide the Real Command Executor Stamp to the Callbacks Mock
* feat: Let Themes Focus Fields by Their Edge and Size Fields and Labels
Shared fields drew a fixed 40px control that could only focus with the
keyboard ring, and Label a fixed text-sm at leading 1, so a theme could not
draw Click UI's 32px field that swaps its stroke on focus, or its 500
0.75rem/1.5 field label.
Fields now read fieldHeight and fieldFocusStyle: ring keeps today's
keyboard-only ring, border swaps the edge to border-field-focus on any focus
with no ring, mirrored on the root as data-theme-field-focus so the pointer
modality reset leaves it alone. Label reads labelSize, labelLeading and
labelFontWeight. Every default reproduces today's field and label; the edge
color follows focus-control and the label size textSm for a theme that
names only those. The ClickHouse theme takes Click UI's field height,
active stroke and label typography, and the drift guard pins them. The
shared Badge, which no app surface renders, keeps a recorded deviation.
* fix: Keep the Pointer Focus Reset for Edge-Focused Fields
Under fieldFocusStyle border the pointer-modality rule was skipped whole,
so a pointer-focused field lost its outline and ring reset along with the
edge reset. Only the edge reset now depends on the focus style.
* fix: Keep the Forced-Colors Outline and Give SecretInput the Field Roles
Under forced colors the edge color and ring drop out, so suppressing the
outline of an edge-focused field left keyboard focus invisible there. The
suppression now applies outside forced colors only.
SecretInput hard-coded h-10 and was not a shared field, so beside an Input
it kept 40px and missed the theme's focus treatment. It now composes
fieldControl, keeping its trailing padding for the controls; its keyboard
focus becomes the same focus-control ring the other fields draw.
* fix: Give Fields a Vertical Padding Role So a Short Field Keeps Its Line
The field kept a fixed py-2 inside the themed height, so ClickHouse's 32px
field left 14px for a 21px line. Fields now read fieldPaddingY, py-2 by
default; the ClickHouse theme takes Click UI's field.space.y, which fills
its 32px exactly, and the drift guard pins it.
* fix: Keep a 2px Keyboard Focus Perimeter and Respect Scoped Edge-Focus Roots
An edge-focused field showed keyboard focus only as its recolored 1px
edge, under the 2px perimeter the app holds as its focus floor. Keyboard
focus now adds a 1px ring in the same color; pointer focus stays edge-only.
The pointer reset checked only the document root for edge focus, so a
border-focus theme applied to a nested root had its edge reset to the
stock border. It now skips any field under an edge-focus root.
Every send moved the thread's tail (isSubmitting, latestMessageId,
latestMessageDepth, and a handleContinue rebound per turn), and the memoized
row context listed all of them as dependencies, so each move handed every row
a new context object and re-rendered the whole thread: three commits of
~12,000 component renders on a 246-message thread, one of them inside the
Enter keypress.
- Keep the row context object stable; the tail values are ref-backed getters
for call-time reads, and rows receive them as props that the row comparator
(isSameTailRelation) only reacts to when the row enters or leaves the tail.
- Fork reads the split target through a getter at click time.
- HoverButtons subscribes to a boolean isSubmitting context and a stable
operations context instead of the combined messages-view context; Fork and
Feedback are memoized so the per-send toolbar pass stops there.
- Make handleContinue referentially stable.
- Cache the Intl formatters behind getMessageTimestamp per locale and clock.
- Add a submit-lag benchmark (e2e/benchmarks-tree) that reports long tasks,
Enter-to-row latency, a CPU profile and per-commit render reasons.
* feat: Show Exit Status for Attached Workspace Commands
Parse the exit trailer the attached-workspace bash_tool writes so the card
fails a non-zero exit, a signal or a timeout, names the reason beside the
failure suffix, and renders stderr distinctly. The group outcome reads the
same parser so its failed count matches the card. Sandbox output without the
trailer keeps the existing heuristics.
* fix: Parse Exit Status Only for Attached Workspace Calls
The sandbox and attached-workspace tools are both named bash_tool, and the
sandbox output is trimmed, so a sandbox command that printed
"[exit code: 1]" last was read as a failed attached-workspace run by the
card and the group outcome.
The execute handler now records a run step when the resolved tool instance
is the one createAttachedWorkspaceBashTool built (tracked by object
identity), and the step-completed handler stamps executor:
'attached_workspace' on the streamed tool call and the aggregated part.
Redis replay and the client SSE merge carry the field through. BashCall
and outcome.ts parse the trailer only when the marker is set.
* fix: Count Styled Terminal Lines Like Plain Ones When Output Ends in a Newline
* feat: Expand, Copy and Tail Long Bash Output
Render bash output through OutputRenderer with a terminal variant: the
collapsed view keeps the last 15 lines, where failures land, with Show more
and a Copy output button; JSON stdout stays verbatim. The sandbox empty-stdout
notice renders as a localized "No output" state, and the command wraps at the
prompt size despite the global code.hljs rule.
* fix: Keep Terminal Output Verbatim Including Leading Whitespace
* fix: Keep Whitespace-Only Output and Ignore the Final Newline When Tailing
* fix: Alias the Button Fills to the Inverted Surface and Size the Legacy Dialog Action
A stylesheet that repainted --surface-inverted or its hover no longer
reached primary buttons, because the stock CSS declared their fills from
palette steps. They now read the inverted surface they split from.
A templated dialog's legacy selection action kept a fixed h-10 and the
inverted fill beside the shared cancel Button, so a theme's button height
split the two. It now reads the Button's height and primary fill roles.
* feat: Give OGDialog Theme Roles for Its Edge, Padding and Title
A templated dialog cleared its edge with border-none and set its title at a
fixed text-lg, semibold, display-family heading in the body ink, so a theme
could not draw Click UI's framed dialog or its 700 1.25rem/1.5 title.
OGDialog now reads a stroke width (in border-light), its inline padding and
header gap, and its title's size, leading, weight, family and ink from theme
roles. Every default reproduces today's dialog; the title size, family and
ink follow textLg, displayFontFamily and text-primary for a theme that names
only those. The ClickHouse theme takes Click UI's dialog stroke, space.x,
title gap, title typography and title color, the drift guard pins them, and
the parity probes now read the dialog stroke and scrim.
* fix: Keep the Dialog Title Ink Out of the Verified Mark's Surroundings
The dialog title color was added to the surfaces the verified mark is
measured against, so a theme that named only the title ink took the
verified fallback. It is a text color, not a surface the mark sits on.
* fix: Let Dialog Titles Take the Dialog Title Ink
Seven dialogs set text-text-primary on their OGDialogTitle, which Tailwind
Merge kept over the new dialog-title role, so a theme that gives dialog
titles their own ink reached only some of them. The redundant classes are
gone; the role defaults to the primary ink, so nothing changes by default,
and the design-rule counts for those files drop by the override each
removed.
* feat: Give the Default Avatar and Avatar Placeholder Theme Roles
The default user avatar filled with a literal rgb(121, 137, 255) in Avatar, MessageIcon and the endpoint Icon, and agent and assistant avatars sat on surface-secondary in light and a dark: surface-tertiary override, so no theme could repaint either.
avatar-fill and avatar-text paint the default avatar and its glyph, and avatar-placeholder paints the backdrop behind an agent or assistant image. Every bundled theme reproduces today's pixels. A theme that sets only its surfaces keeps the placeholder on the surface its mode used before the role existed, both when resolved and through the legacy applyTheme path. ClickHouse takes Click UI's avatar fill and text and its muted background.
* test: Pin the Default Avatar Fill With and Without the ClickHouse Theme
The sidebar account avatar falls back to the default avatar when its image fails; with no theme it keeps rgb(121, 137, 255) in both modes and the placeholder keeps the surface its mode used, and under ClickHouse both take the Click UI values.
* fix: Ink Every Default Avatar Glyph With the Avatar Text Role
The sidebar Avatar, the only default avatar the chat renders, still inked its glyph in text-primary, so a theme's avatar-text never reached it and ClickHouse drew a dark glyph where Click UI draws white. Avatar now reads avatar-text, which defaults to each bundled theme's primary text and follows rgb-text-primary in a theme that does not set it, through resolveTheme and the legacy applyTheme path, so every rendered default avatar keeps its pixels.
* fix: Read the Active Mode Off the Root When applyTheme Is Not Told It
applyTheme is exported, and a caller that applies a legacy palette in dark mode without the new mode argument derived the avatar placeholder from the light surface. It now falls back to the root's dark class.
* fix: Keep CSS-Themed Avatars on Their Legacy Source Variables
The avatar text and placeholder defaults were literal triplets, so a consumer theming through --text-primary and the surface variables left avatars on the stock colors. They now alias text-primary, the secondary surface and, in dark, the tertiary surface, resolving to the same pixels by default. applyTheme's mode fallback also reads a dark ancestor, not only the root itself.
* fix: Let the Stylesheet Alias Carry the Document Root Avatar Backdrop
applyTheme wrote the legacy placeholder inline for the mode active when it ran, which then overrode the per-mode stylesheet alias after a dark toggle without a reapply. On the document root the alias already follows the theme's surfaces and the mode, so the placeholder is now derived only for a scoped root, which that alias cannot see.
* fix: Keep a Scoped Legacy Avatar Backdrop Following the Mode
applyTheme wrote a scoped root's avatar placeholder inline for the mode active when it ran, so after a later dark toggle the backdrop stayed on the light surface, where canary's dark:bg-surface-tertiary switched. applyTheme now marks a scoped root with data-theme-scope and the stylesheet points its backdrop at that root's own secondary surface, or its tertiary one under a .dark ancestor, as the document root's alias does. The mode argument is no longer needed and is removed.
Pin every Click UI parity decision to its verdict per mode (match, near, deviation, not expressible) instead of aggregate floors, so a swap fails by name. List the decisions no theme can reach today, each with its reason and tracking issue, and print a match/near/mismatch status for every color and appearance role against the Click UI token that names its job.
Every status is measured from a rendered primitive or a cited snapshot token: a missing token, a stylesheet rule the rendered popover no longer takes its corner from, a size or radius class no role resolves, an empty gap entry or a moved appearance decision all fail by name. The Button primary fill and height now match through the Button roles, so the Button leaves the list.
* feat: Group the model parameters and drop the ones that cannot act
The panel rendered a provider's parameter list in the order the definitions
happen to arrive in, so it asked about temperature, then reasoning, then
whether to resend files, with nothing to say which belonged together. The
keys are filed under six headings now, with a count beside each of what this
conversation has changed inside it, which is what the owner scans for before
reaching for Reset. A key this map has never heard of, which is what a
deployment's own customParams look like, keeps its place in the last section
instead of being guessed at or dropped.
Every parameter stays on screen. A settings panel is read as much as it is
edited, and a disclosure trades seeing the current state at a glance for
vertical space that costs nothing to find elsewhere: the headings are
captions rather than buttons, a control is measured against the row it sits
in rather than padded to a fixed block, and only free text takes the full
width. A number, a toggle or a choice says the same thing in half of a 300px
panel, so two sit side by side and the narrow ones in a section come first,
leaving one ragged edge at the bottom instead of a gap beside every
full-width field. Reset and Save As Preset share the closing row. Fifteen
parameters occupy 954px where the same fifteen took 1243px with four of the
six sections shut.
Grouping alone would still show controls that do nothing. A definition can
now declare what it rides along with: OpenAI's reasoning summary, mode and
context travel inside the reasoning object the Responses API takes and are
dropped by the server without it; a thinking budget is read only while
thinking is enabled; a cache lifetime only while the cache is being written.
Those five declare it, the panel judges each one on the companion's
effective value, and a section left with nothing live disappears rather than
standing empty. The rule lives on the definition rather than in the panel so
a deployment defining its own parameters can state one too.
The custom instructions field caps its own rows. It is sized by a shadow
copy of itself, measured as the panel mounts and before the sidebar has
settled on a width, and that measurement can come back as one word per line;
a CSS max-height was hiding the wrong answer rather than correcting it.
No parameter changes what it sends. This drops controls for values the
server was already discarding.
* refactor: Keep every model parameter on screen and drop only empty controls
Hiding a parameter behind a companion toggle judged it by a rule the
client cannot see all of: a reasoningObject endpoint sends the reasoning
fields without the Responses API, adaptive-thinking Claude models ignore
the budget however thinking is set, and a deployment could not declare
the rule in librechat.yaml at all. The panel groups every parameter again
and leaves out only a choice with no options, such as Bedrock's region
when no regions are configured, so no section stands empty. Reset and
Save As Preset share a row while their labels fit and stack when a
translation is too long for the panel.
* test(e2e): Scenarios for the grouped model parameters panel
* fix(client): Wrap a parameter action label longer than the panel
A Spanish Save As Preset label measures 338px on its own against a 282px
row, so stacking the two actions still ran it past the panel. The labels
now wrap inside their buttons.
* fix(client): Scope stretched controls to the panel and say what its counts mean
The shared parameter controls stretched to their parent's height, which
the preset editors' tall columns turned into labels far above their
fields; the panel's cells now stretch their controls instead. The change
count beside a heading is read out as a number of changed settings, and
clearing a default a deployment configured counts as a change.
* test(e2e): Scenario for the preset dialog's label spacing
* feat: Give the Button Theme Roles for Its Label, Height, Fill and States
The Button drew a fixed 500-weight label at 40px and 36px, painted its
primary fill in the inverted surface its checkbox and switch share, focused
in the primary ink, and only dimmed when disabled, so a theme could not
draw Click UI's 400-weight 32px buttons or its #302e32 primary.
Add controlFontWeight, buttonHeight and buttonHeightSm appearance roles and
button-primary and button-primary-hover color roles, which follow the
inverted surface for a theme that names only that. The Button reads them,
focuses in focus-control, presses in the pressed roles and composes the
shared disabled recipe; the defaults reproduce today's button exactly.
Tailwind Merge now knows the new utilities, so a caller's own height or
weight still wins.
SelectTrigger hid its outline on every focus and drew nothing instead; it
now draws keyboard focus in focus-control, like the shared field.
The ClickHouse theme takes Click UI's label weight, button height and
primary fills, and the drift guard pins them and measures the Button.
* fix: Focus the Shared Inputs in the Focus-Control Role and Repair the Button Specs
SecretInput, MultiSearch, InputWithDropDown and InputCombobox drew keyboard
focus in the decorative ring-primary, about 2.3:1 on the dark default canvas.
They now use focus-control, and a guard holds that role at 3:1 on every
control canvas in each theme. The Scrim spec follows the Button's focus role,
and the button-roles scenario opens the Data & Privacy tab by its current name.
* test: Reach the Shared Input Focus Rings by Keyboard
The focus-role guard read component source, which a dead string or a ring on a
non-focusable wrapper would satisfy. Each control is now reached by Tab and
the focused element, or the combobox's ring host while it holds keyboard
focus, is asserted to paint the focus-control ring.
* feat: Give Theme-Sized Controls Their Own Padding and Gap Roles
The theme variants of Button and Chip, CheckboxButton and every composer
control read spaceNormal and spaceCompact, which also pad message rows,
steer bubbles and the composer send button, so a theme could not give its
controls Click UI's button spacing without reshaping the chat.
Add controlPaddingX and controlGap appearance roles, which those controls
read instead. Their defaults are the shared spacing values, a theme that
names only spaceNormal or spaceCompact keeps its controls on them, and the
preset falls back to the shared roles for a stylesheet that predates these.
The ClickHouse theme takes Click UI's button.basic.space.x and space.gap,
and the drift guard pins both values and measures the themed Button's
padding and gap.
* test: Reach the Temporary Chat Chip Through a Sent Message
The header status chip only appears once a temporary chat has its first message, so the scenarios send one, and measure the real message bubble instead of a probe for the shared spacing.
* fix: Let the Control Spacing Roles Replace the Base Gap
Tailwind Merge could not classify px-theme-control-x or
gap-theme-control-gap, so a theme-sized Button kept the base gap-2 beside
the role and a caller's own padding beside both, leaving the winner to
stylesheet order. Register both utilities with their groups.
* fix: Alias the Stock Control Spacing to the Shared Spacing Roles
A stylesheet that set only --theme-space-normal or --theme-space-compact
stopped reaching Button, Chip and the composer controls once the stock CSS
declared the control roles as literals, so the preset's fallback never ran.
The stock declarations now read the shared roles, with the same defaults.
* test: Assert the Control Spacing Utilities Declare Their Own Properties