Skip to content

fix(app): prompt to connect when creating a browser automation with no connection - #3518

Merged
tofikwest merged 1 commit into
mainfrom
fix/browser-automation-create-needs-connection
Jul 28, 2026
Merged

fix(app): prompt to connect when creating a browser automation with no connection#3518
tofikwest merged 1 commit into
mainfrom
fix/browser-automation-create-needs-connection

Conversation

@tofikwest

@tofikwest tofikwest commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

The bug

On an evidence task with no connections (e.g. after deleting them), the Browser Automations section still showed "Create Browser Automation" — but clicking it did nothing.

Root cause

The button sets composer.open = true, but the composer only renders when composer.open && composerConnection (BrowserAutomations.tsx:365). With no connections, composerConnection resolves to null (buildConnectionRef falls through to return null), so the composer never opens and the screen falls back to itself — a silent no-op.

The deeper issue: an automation can only be built on an existing connection, but the empty-state offered "Create" regardless of whether one existed.

The fix

Decide the no-automations empty state by whether a connection actually exists:

  • No connection (and none just made — the profile list refetches a beat after connecting) → show "Connect a vendor login" first (clickable, correct next step).
  • Has a connection → show "Create Browser Automation" as before.
  • Drafts are still surfaced above either way, so nothing in progress is lost.

Verification

Typecheck clean. No test harness exists for this orchestrator component (wires ~10 hooks); verified by tracing the render/composer conditions. Best confirmed live: on a task with zero connections, the section now shows the clickable "Connect a vendor login" instead of a dead "Create" card.


Summary by cubic

Fixes a dead "Create Browser Automation" button by prompting to connect a vendor login when the task has no connections. Drafts still show, and "Create" appears once a connection exists.

  • Bug Fixes
    • If no connection exists, show "Connect a vendor login" instead of "Create Browser Automation".
    • Keep drafts visible via the drafts strip in both states.
    • Ensure the composer only opens when a connection exists, removing the no-op click.

Written for commit 2b1dcad. Summary will update on new commits.

Review in cubic

…ction

With no connections, the task still showed 'Create Browser Automation', but the
composer only opens when a connection exists (composerConnection resolves to
null otherwise) — so the button silently did nothing. Decide the empty state by
whether a connection actually exists: no connection (and none just made) now
shows 'Connect a vendor login' first; drafts are still surfaced to resume.
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment Jul 28, 2026 4:27pm
comp-framework-editor Ready Ready Preview, Comment Jul 28, 2026 4:27pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
portal Skipped Skipped Jul 28, 2026 4:27pm

Request Review

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Re-trigger cubic

@tofikwest
tofikwest merged commit 631d87a into main Jul 28, 2026
11 checks passed
@tofikwest
tofikwest deleted the fix/browser-automation-create-needs-connection branch July 28, 2026 16:31
@claudfuen

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.110.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants