molecule-ai/molecule-core
52
0
Fork 2
Code Issues 175 Pull Requests 17 Actions 6 Packages Projects Releases Wiki Activity

chat UX: persist in-flight exchange across leave/refresh + bottom-sticky autoscroll for accumulating tool calls (CTO) #2560

New Issue
Open
opened 2026-06-10 23:28:43 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-10 23:28:43 +00:00
Member
Copy Link
Copy Source

Two CTO asks (2026-06-10/11), one PR or two:

1. Chat must persist across leave/refresh — today returning mid-turn shows ONLY the typing dots.
Mechanism: useChatHistory.loadInitial hydrates from /workspaces/:id/chat-history (DB), but the user's outgoing message is only appended to LOCAL state (onUserMessage) and the server writes chat-history rows at turn completion — so on remount mid-turn the current exchange is missing entirely (worst on a fresh agent with no prior history: empty pane + dots).
Fix (both halves):

  • Server: write the inbound user chat message to chat history at RECEIPT (not completion), flagged/ordered so the eventual agent reply lands after it. Idempotent on messageId.
  • Client: on mount, if the workspace has an active turn (active task / send-in-flight state from the server), restore the thinking indicator + elapsed timer instead of starting blank; hydrated history now includes the pending user message.
    Tests: hydrate-mid-turn renders the user bubble + dots; completed turn renders both bubbles; no dup when WS reply arrives after hydration.

2. Bottom-sticky autoscroll while tool calls accumulate.
Mechanism: ChatTab's scroll useLayoutEffect deps are [history.messages] — the live activity feed (activityLog, the tool-call lines under the spinner) grows without triggering scroll, so the user manually chases it.
Fix: track atBottom (scroll listener with a small threshold); when at bottom, also scroll on activityLog growth; when the user has scrolled up, NEVER yank (this should also gate the existing message-append smooth-scroll — currently it always scrolls even if the user is reading older history). Preserve the loadOlder scroll-anchor logic untouched.
Tests: activity growth scrolls when at bottom; does not scroll when scrolled up; message append respects the same gate; anchor restore unaffected.

🤖 Generated with Claude Code

Two CTO asks (2026-06-10/11), one PR or two: **1. Chat must persist across leave/refresh — today returning mid-turn shows ONLY the typing dots.** Mechanism: `useChatHistory.loadInitial` hydrates from `/workspaces/:id/chat-history` (DB), but the user's outgoing message is only appended to LOCAL state (`onUserMessage`) and the server writes chat-history rows at turn completion — so on remount mid-turn the current exchange is missing entirely (worst on a fresh agent with no prior history: empty pane + dots). Fix (both halves): - **Server**: write the inbound user chat message to chat history at RECEIPT (not completion), flagged/ordered so the eventual agent reply lands after it. Idempotent on messageId. - **Client**: on mount, if the workspace has an active turn (active task / send-in-flight state from the server), restore the thinking indicator + elapsed timer instead of starting blank; hydrated history now includes the pending user message. Tests: hydrate-mid-turn renders the user bubble + dots; completed turn renders both bubbles; no dup when WS reply arrives after hydration. **2. Bottom-sticky autoscroll while tool calls accumulate.** Mechanism: `ChatTab`'s scroll `useLayoutEffect` deps are `[history.messages]` — the live activity feed (`activityLog`, the tool-call lines under the spinner) grows without triggering scroll, so the user manually chases it. Fix: track `atBottom` (scroll listener with a small threshold); when at bottom, also scroll on `activityLog` growth; when the user has scrolled up, NEVER yank (this should also gate the existing message-append smooth-scroll — currently it always scrolls even if the user is reading older history). Preserve the loadOlder scroll-anchor logic untouched. Tests: activity growth scrolls when at bottom; does not scroll when scrolled up; message append respects the same gate; anchor restore unaffected. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2560
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?