Skip to content

perf: speed up initial chat, channels, skills, and cron loading#901

Merged
su8su merged 1 commit intomainfrom
feat/refine_gateway_start
Apr 23, 2026
Merged

perf: speed up initial chat, channels, skills, and cron loading#901
su8su merged 1 commit intomainfrom
feat/refine_gateway_start

Conversation

@su8su
Copy link
Copy Markdown
Contributor

@su8su su8su commented Apr 23, 2026

No description provided.

@su8su su8su merged commit 5137e70 into main Apr 23, 2026
5 checks passed
@su8su su8su deleted the feat/refine_gateway_start branch April 23, 2026 10:49
Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 39ee1d8f20

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +140 to +143
await Promise.allSettled([
loadSessions(),
loadHistory(hasExistingMessages),
]);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Load sessions before starting history fetch

Running loadHistory() in parallel with loadSessions() introduces a startup race: if history for the old currentSessionKey returns first, it can populate messages for that old session, and then loadSessions may switch currentSessionKey without clearing those messages (see src/stores/chat.ts in loadSessions). That leaves the newly selected session showing the wrong transcript until another history load completes, and if that follow-up load fails the stale messages can persist because history failures keep existing messages. Please restore ordered loading (sessions first, then history) or clear messages when currentSessionKey changes.

Useful? React with 👍 / 👎.

DigitalNomad-Chat added a commit to DigitalNomad-Chat/ClawX that referenced this pull request Apr 26, 2026
…docs update (ValueCell-ai#863 ValueCell-ai#900 ValueCell-ai#901 ValueCell-ai#905 ValueCell-ai#910)

Remove provider setup step, speed up initial loading, remove brave-web-search,
update READMEs for LaTeX, add agent context files, strip first run sections.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant