Fix sending messages during active turns

[jakeleventhal]

What changed

• track the latest projected user message in the local dispatch snapshot
• acknowledge sends that add a steering message to an already-running turn
• add regression coverage for steering without a new turn or timestamp change

Why

Messages sent while an agent was already working remain on the current turn. The composer only recognized server acknowledgment when turn metadata changed, so its local sending state could remain stuck until the thread was remounted by navigating away and back.

This change also treats the newly projected user message as acknowledgment, allowing subsequent steering messages without thread navigation.

Validation

• pnpm exec vp test apps/web/src/components/ChatView.logic.test.ts
• pnpm exec vp check
• pnpm exec vp run typecheck

Note

Fix message sending during active turns by recognizing steering messages as server acknowledgment

• hasServerAcknowledgedLocalDispatch now returns true during a running turn when the latest user message ID changes, treating a projected steering message as server acknowledgment
• LocalDispatchSnapshot gains a latestUserMessageId field, captured via findLast over messages with role === 'user' at snapshot creation time
• ChatView.useLocalDispatchState passes the current latestUserMessageId into the acknowledgment check, clearing activeLocalDispatch and unblocking isSendBusy sooner when a steering message appears

^{Macroscope summarized d84bb40.}

---

Note

Low Risk
Targeted chat UI state logic with unit tests; no auth, data, or API surface changes.

Overview
Fixes the composer staying in a Sending / busy state when users send steering messages while a turn is already running.

Local dispatch acknowledgment now records the latest user message id in LocalDispatchSnapshot and passes the live id from useLocalDispatchState. During the running phase, hasServerAcknowledgedLocalDispatch treats a change in that id as server acknowledgment—even when turn metadata is unchanged—so activeLocalDispatch clears and isSendBusy recovers without navigating away.

Regression coverage adds the steering-on-current-turn case in ChatView.logic.test.ts.

^{Reviewed by Cursor Bugbot for commit d84bb40. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 503bd64d-c58c-4b8c-80ea-3ce9fbe5bf39

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9361c84. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Straightforward bug fix that adds tracking for the latest user message ID to properly acknowledge steering messages during active turns. The change is self-contained with clear intent, good documentation, and comprehensive test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9361c84e3b

ℹ️ 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".

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

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[QarthO]

For those who also come across this issue/waiting for it to be merged,

a current workaround you can do is swap to a different thread, then come back to the broken thread and you're able to send messages again