🔑 refactor: Read Stream Auth and Deployment Config Through ChatSettings

[berry-13]

Pull Request

Before submitting, please review the Contributing Guide.

Documentation changes belong in the LibreChat documentation repository.

Summary

The stream hooks still reached into the app for two globals: useResumableSSE, useSSE and the abort handlers read the bearer token and sign-in state from useAuthContext, and useResumableSSE, useSSE and useResumeOnLoad read the balance toggle, the retention mode and whether the startup config has arrived from useGetStartupConfig. That ties the chat hooks to the app shell instead of the host-supplied ChatSettings the rest of the chat already reads.

This adds token and isAuthenticated to ChatAuth, and loaded and balanceEnabled to ChatConfig, fills them in ChatSettingsProvider from the same queries, and switches the four hooks to useChatSettings(). The new fields are optional: a host that does not set loaded has no config to wait for, matching the default settings used in isolated renders. No behavior changes: the provider wraps every route that mounts these hooks. Stacked on #17138.

Type of change

• Refactor

Testing

Tested environments/configuration:

Not applicable: the hooks receive the same values through the settings context instead of reading them directly.

Automated tests:

• ChatSettings.spec.tsx covers the new fields: loaded and balanceEnabled are false until the deployment answers and follow it after, and the signed-in token reaches auth.
• useResumeOnLoad.spec.tsx drives the retention mode and the "config not yet loaded" wait through the settings context; transport.spec.tsx and useResumableSSE.spec.ts supply the token through it instead of mocking useAuthContext.
• In client: hooks/SSE, hooks/Chat, routes and components/Chat: 250 suites, 4,741 tests pass.
• npx tsc --noEmit in client, eslint, prettier and sort-imports on the changed files: clean.

Screenshots / recordings

No user-facing change.

Risk / compatibility

None for users. A host that renders the chat hooks outside ChatSettingsProvider would now stream without a token; the app mounts them only under Root, which supplies it.

Checklist

• I reviewed my own changes
• Relevant tests have been added or updated

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-16T19:40:15.728294Z	907b2a0	New commits
🔒 Security Review	✅ Completed 2026-10-15T07:57:21.333559Z	a4795a6	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.