fix(tui): prevent duplicate message forks - #38240
Merged
Merged
Conversation
opencode-agent
Bot
force-pushed
the
fork-once
branch
2 times, most recently
from
July 22, 2026 04:04
9cc953e to
199ebbd
Compare
opencode-agent
Bot
force-pushed
the
fork-once
branch
from
July 22, 2026 14:28
199ebbd to
0f3707f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/forkpicker unchangedRoot cause
The message action path starts the fork from
DialogFork.onMount. It previously initializedpendingto false, then immediately changed it to true; that reactive update remounted the stored dialog accessor, firingonMountand the non-idempotent fork request repeatedly.Checks
bun typecheck(packages/tui)bun test test/app-lifecycle.test.tsx --timeout 30000(packages/tui)Closes #38238
Requested by: @rekram1-node (Aiden Cline via Slack)