useAdaptiveSSE and useResumableSSE now live in the chat package and own the
run, the stream id and how a stream re-attaches. The app supplies the services
a resumable stream runs on and the Assistants stream through a StreamHost,
mounted in Root beside the chat and steer hosts.
useChatHelpers now builds the pane contract from a ChatHost the app supplies:
its pane store, message query cache, turn builder, thread selection, abort
transport and settings. The stop path lives in its own module, its spec runs
in the package against a host with no app behind it, and the app mounts its
host in Root beside the steer host.
* refactor: Move the useChat Facade and ChatContext into @librechat/chat/react
The facade, ChatContext, the chat contract types and the resume request atom now
live in the chat package. The message cache subscription and the app's tool
outcome rules reach the facade through the contract, and useChatHelpers reads
its pane conversation through ChatSettings instead of the app store.
* fix: Key Cached Message Views on the Host's Tool Outcome Rules
* 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.
* 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
* refactor: Move text-like message parts into @librechat/chat
Text, EmptyText, CollapsibleText, Summary and AgentUpdate move into the package's components entry with their unit specs and read the app only through MessagePartsHost, which gains renderMarkdown, useSmoothStreaming, useAgent and renderAgentIcon. The app's markdown and agent-icon renderers register from the Parts barrel, so the host module keeps its import graph.
The design-suppression runner compares a moved file's diagnostics by their first sentence: the remedy that follows names app-only compositions for client paths, so the same violation read as new after a move.
* test: Cover text-like parts rendered from @librechat/chat in the browser
* feat: Add Approval-Responded, Output-Denied and Ask-User Parts to the UI Message View
* refactor: Accept the Ask-User Pause in the Part Mapper Input Type
* fix: Keep the Reviewer's Output on a Respond Decision
* fix: Keep a Respond Decision's Output Successful When It Reads Like an Error
* refactor: Lift the step handler branches into a core reduceStep
The stepHandler branches move to @librechat/chat as reduceStep(state, event, ctx), with the per-run maps in a StreamState and every write outside the message list returned as a StepEffect. useStepHandler keeps the frame coalescing and applies the effects to the Jotai and Recoil stores.
The equivalence spec runs a frozen copy of the previous hook against the new binding on each recorded sequence and compares every channel they write.
* test: Pin the step reducer equivalence digests and drop the frozen handler
* test: Load the step reducer from the built chat core
* test: Type the equivalence fixtures to the event unions
* ci: Type-Check Workspaces with bun check
Make every workspace tsconfig valid under TypeScript 7 semantics while
staying clean on the installed tsc 5.9: explicit types arrays (TS 7 no
longer auto-includes node_modules/@types), es2017 target for
data-provider, rootDir for api specs that import client contracts, and
noUncheckedSideEffectImports off for the CSS and matchMedia mock imports.
Fix the four client type errors newer DOM and Intl libs expose, and drop
the fetch.preconnect copy in useRum that only existed to satisfy the
leaked @types/bun globals.
Switch the client typecheck script and the CI type-check steps to
bun check (Bun 1.4.3); tsc --noEmit stays available as typecheck:tsc.
* chore: Fall Back to tsc When bun check Is Unavailable
Add scripts/typecheck.mts, which runs bun check when the installed Bun
provides it and the repository's tsc otherwise, so contributors without
Bun can still type-check. The client typecheck script and the
static-checks TypeScript gate both resolve their checker through it,
keeping local runs on the same checker CI uses whenever Bun is present.
* ci: Type-Check the Chat Package Through the Shared Checker
* ci: Run the Type Check When Only the Shared Checker Changes
A change to scripts/typecheck.mts alone started neither frontend review
nor the static-checks TypeScript gate, so a broken resolver could merge
unexercised. Add it to the frontend-review triggers and to every
typecheck project's paths.
The suppression-baseline scenarios copy static-checks.mts into synthetic
roots; copy its new typecheck.mts import alongside i18n.mts so the runner
loads there. Add scenarios for the checker choice and its fallback.
The step appliers, frame normalizer and SSE transport move from client/src/hooks/SSE into packages/chat/src/core with their specs, and the client imports them from @librechat/chat. The ask-user-question predicates the content applier reads move with them, and the client's approval module re-exports them so its consumers are unchanged.
* feat: Scaffold the @librechat/chat package
Adds packages/chat with core, react and components entries, a tsdown build,
a node-environment jest config, turbo and root build wiring, import boundary
rules, design-lint scope, and core types for the chat transport, stream,
host and status. No code moves yet.
* test: Cover the @librechat/chat boundaries as scenarios
* fix: Run the chat suite in test:turbo and build it for the mock lane
test:turbo now selects @librechat/chat, the mock e2e job builds the package the
chat-package scenarios load, and the synthetic repository in the suppression
scenarios carries the packages/chat/src root lint:design:record names.
* chore: Build the chat package in frontend:ci too
* chore: Run the chat suite in test:all
* fix: Hold core TSX to the chat boundary and scan the package for cycles
* fix: Apply the chat import boundary to JavaScript sources
* fix: Keep nested core files off the components entry
* fix: Close the remaining chat package gates and fence aborts by generation
Blocks imports through the @librechat/frontend workspace name, adds the chat
sources to the i18n scan, the CSS color gate and the client Tailwind content,
and lets ChatAbortRequest carry the generation it means to stop.
* fix: Keep JSX out of the chat core and carry abort and reconnect outcomes
Rejects JSX under the core, copies the chat manifest before the Docker
install, keys the client app build caches on the chat sources, fences
reconnects by generation, and types the abort result the transport returns.
* test: Give the CSS gate's scratch tree the chat root it now scans
* fix: Close the remaining @librechat/chat gates and wiring
Rejects import() and require() across the package boundaries, holds chat
components to the literal-copy rule, compiles TSX in the package's jest
transform, builds the package in Frontend Unit Tests, requires its test job for
main promotion, adds it to the unused-dependency scan, and lists it wherever a
sibling workspace is listed: Dockerfile.multi, the docker smoke paths, the
remaining node_modules caches, the reinstall helper, the bun build chain and
AGENTS.md.
* fix: Tighten the chat boundaries and carry steering and Assistants aborts
Template-literal import() and require() and self-imports through the package
name are rejected, user-facing JSX attributes need localized text, the cycle
scan resolves self-imports, Dockerfile.multi builds the package for the client
stage, and the transport carries steer, cancelSteer, armSteer and the
Assistants abort key.
* feat: Match the chat transport and host contracts to the client's
The transport now reports settled and replaced starts, the stream's protocol
version and resumed flag, reconnect replay, generation status, paused-run
resume with approvals or answers, abort and steer protocol versions, and the
request error shape. The host config and auth carry what the client's
ChatSettings now supplies: rename-while-running, model specs, retention mode
and the user.
* fix: Keep lazy React-entry loads out of the core and type the Assistants stop
Relative import() and require() of the /react entry from core are rejected,
and an abortKey stop resolves to the terminal conversation and run messages the
Assistants route returns.
* fix: Fence start controls by protocol and close extension-bearing entry loads
Settled and replaced start results carry the protocol version, core loads of
the /react or /components entry with a file extension are rejected, and
test:packages:chat builds data-provider first.