Windsurf Cascade can help edit code and inspect a local preview, but a preview is not automatically the same browser profile as your signed-in production or staging tab. Windsurf’s own docs now label Cascade as legacy in Devin Desktop, while its current docs cover Windsurf Previews separately. For an authenticated visual check, keep Cascade focused on the code and local preview, then use Tabbit Browser + Tabbit CLI on the same machine to inspect the real signed-in site. Verify the host and route before trusting either view.
In a 2025 Reddit thread, a user said the in-IDE preview did not let them log in to their app, while another commenter recommended using a separate browser (discussion). A separate thread reports loss of element and console handoff after the dedicated browser was deprecated (thread). These are dated user reports; Windsurf behavior changes by release, so re-check the current app rather than applying them as universal rules.
Key takeaways
Use the local client and verify its actual Skill or shell access.
Check the signed-in page with a harmless read before asking for research.
Save an explicitly named draft and keep a human review checkpoint.
The browser path at a glance
| Surface | Where it runs | What to verify |
|---|---|---|
| Cascade editor | Editing code, reading repository context | Does not itself prove page access |
| Windsurf Preview | Reviewing a local app and sending selected UI/error context | Preview context is separate until verified |
| System browser | Manual visual review in a browser you choose | May not send element/error context to Cascade |
Verify the client before the session
The current Cascade documentation labels Devin Desktop Cascade as legacy. Separate three things before testing: (1) the local dev server and its preview URL, (2) any Windsurf in-IDE preview or system browser mode supported by your current version, and (3) the Tabbit profile that holds the site login. Windsurf Preview is designed to relay selected elements or console errors to Cascade, but that does not establish that it can reuse a separate browser’s cookies. Tabbit CLI can run a separate browser task while you continue using other tabs. Do not assume the old “Windsurf Browser” remains available or that cloud Cascade can reach a local desktop profile.
A practical Tabbit workflow for this task
Use a two-pass review. First ask Cascade to identify the changed component, expected visual states, and local route, then inspect its Preview for layout defects. Next ask a local agent with Tabbit Skill to open the corresponding signed-in staging route and create cascade-visual-review-draft.md with route, visible state, and discrepancy. A synthetic fixture is useful for testing the handoff, but label it as a fixture. Do not let either agent publish, submit a form, or treat a preview screenshot as proof of production behavior.
Use this prompt as a bounded template. Replace internal paths with approved inputs; the sample is not a claim that the named content exists.
Open the approved staging route in the signed-in Tabbit profile. Check the target component in its default, loading, and empty states. Label each observation with the route, environment, and visible result. Compare with the local preview notes. Save `cascade-visual-review-draft.md` and leave the site unchanged for review.A decision table for the handoff
| Stage | Check | Evidence |
|---|---|---|
| Build preview | Run the project’s approved local command | Expected localhost route and commit/worktree |
| Review layout | Use current Windsurf Preview or manual browser | Screenshot or issue list; label preview mode |
| Check authenticated page | Open the target route through Tabbit CLI | Observed title, route, and key visible state |
Related setup guides
For another client, the same order applies: discover the client skill, check local launcher reachability, verify the signed-in host, then save a reviewable draft. See the Tabbit CLI guide. Start with a test page you can inspect manually, and keep the site action read-only.
FAQ
Is Windsurf Preview the same as my signed-in browser?
Do not assume so. Check the current preview mode and verify the target page in the profile that owns the login.
Can Cascade inspect a local app?
Windsurf Previews are intended for local app review and can relay selected elements or errors. Availability and behavior depend on the current release.
Is the old Windsurf Browser still available?
The official docs call Cascade in Devin Desktop legacy, and Windsurf announced its Browser deprecation. Re-check the current product version.
Can Cascade use Tabbit cookies?
No documented native cookie handoff is assumed here. Use Tabbit CLI locally to inspect the Tabbit profile.
What should a visual review draft contain?
Record the route, visible state, discrepancy, source screenshot or page, and reviewer status.
Can this verify production?
A local preview verifies the local app only. Check production separately and do not infer production behavior from a fixture.