-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Claude native: report blocking startup dialogs without closing the terminal #7969
Copy link
Copy link
Closed
Closed
Copy link
Labels
BugSomething isn't workingSomething isn't workingP1-highPriority: major feature broken, no workaroundPriority: major feature broken, no workaroundcomp:harness-t1Highest-usage harnessesHighest-usage harnessescomp:runnerComponent: agent runner, execution engineComponent: agent runner, execution enginetriagedIssue has been triaged by the botIssue has been triaged by the botvalidated:reproducedRepro agent validated the issue can be reproducedRepro agent validated the issue can be reproduced
Description
Activity
Metadata
Metadata
Assignees
Labels
BugSomething isn't workingSomething isn't workingP1-highPriority: major feature broken, no workaroundPriority: major feature broken, no workaroundcomp:harness-t1Highest-usage harnessesHighest-usage harnessescomp:runnerComponent: agent runner, execution engineComponent: agent runner, execution enginetriagedIssue has been triaged by the botIssue has been triaged by the botvalidated:reproducedRepro agent validated the issue can be reproducedRepro agent validated the issue can be reproduced
Description
When a startup dialog appears while the Claude native bridge is waiting for its input box, the first web message waits until the readiness timeout. The executor then closes the terminal, destroying the dialog the user needed to answer.
MCP pre-approval (#7946) prevents one common trigger, but the readiness gate still needs to recognize other blocking selection/confirmation dialogs. This is a follow-up to #7945, not a claim that the original reported incident was conclusively caused by a dialog.
Reproduction
Start a host-backed Claude native session in a fresh workspace containing
.mcp.json. For a deterministic regression, delay Claude startup by eight seconds and setenableAllProjectMcpServersto false in its invocation-local settings, preserving the native bridge hooks. Send a web message before Claude renders the MCP approval dialog.Current main (181c829) has no dialog-specific readiness failure. The expected behavior is a prompt error explaining how to answer the dialog, with the same terminal left alive. After answering the dialog and resending, Claude should reply and that reply should appear in the web session.
Scope
Detect stable dialog-shaped terminal output during the readiness wait. Do not add automatic consent, change the existing Escape-based input reclamation, or implement delivery acknowledgments in this change.
Environment
macOS, Claude Code 2.1.269, host-backed
claude-native-ui, real interactive Claude login.