Skip to content

fix(site): disable app buttons when agent is not connected#22100

Draft
stirby wants to merge 1 commit intomainfrom
fix/issue-21954-app-buttons-connecting-state
Draft

fix(site): disable app buttons when agent is not connected#22100
stirby wants to merge 1 commit intomainfrom
fix/issue-21954-app-buttons-connecting-state

Conversation

@stirby
Copy link
Collaborator

@stirby stirby commented Feb 13, 2026

Summary

App buttons (VS Code, Terminal, custom apps) were clickable during the agent
"connecting" state, causing failed connections when clicked. The canClick
logic in AppLink only checked agent.lifecycle_state but not agent.status.

Fix

  • AppLink.tsx: Added check for agent.status !== "connected" to disable
    clicks when the agent hasn't established its connection yet.
  • TerminalLink.tsx: Added disabled prop that removes the href and blocks
    onClick when the agent is not connected.
  • VSCodeDesktopButton.tsx: Added disabled prop that disables the button
    when the agent is not connected.
  • AgentRow.tsx: Passes disabled={agentAppsDisabled} to VSCodeDesktopButton
    and TerminalLink when agent.status !== "connected".

The existing CSS rule [&:is(a):not([href])]:pointer-events-none [&:is(a):not([href])]:text-content-disabled
on the Button component automatically greys out anchor-based buttons when their
href is removed.

Closes #21954

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

App buttons (VS Code, Terminal, custom apps) were clickable during
agent "connecting" state, causing failed connections. The canClick
logic in AppLink only checked lifecycle_state but not agent status.

Closes #21954

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

App buttons are clickable during agent 'connecting' state

1 participant

Comments