What this is
The autonomous-editor flavor of the simple-and-fast path. Windsurf leans toward “tell Cascade the goal and let it execute”, multi-file builds and refactors with less step-by-step steering than a classic copilot. When it’s done you have a real project folder, and Revdoku publishes that folder to a live URL in one command. Build agentically, ship instantly.
When to pick this stack
- You want an agent-first editor that runs further on its own before checking in with you.
- The result is a local project you want online without wiring up a host.
- You’re iterating fast and want each version live at the same shareable link.
How publishing works (Revdoku)
From the project folder, revdoku p . publishes the files and hands back a live URL (install once with curl -fsSL https://revdoku.com/install.sh | bash). Pick the access level:
- Public, open to anyone with the link.
- Password-protected, the link plus a shared password.
- Password + email, a password and the visitor’s email, with optional email confirmation to verify them first.
You get analytics on how the published app is used, and password + email mode breaks it down per visitor, which email opened it and what they did, which is ideal for sharing a prototype with a handful of named testers. Updates go to the same URL, and there’s a free plan to start.
What we’d swap
- Windsurf → Cursor: if you want tighter, diff-by-diff control instead of a more autonomous agent.
- Windsurf → Codex: when you’d rather delegate to a cloud agent than run the build in a local editor.
Common gotchas
- A more autonomous agent means more to review: read what Cascade changed before publishing, especially new dependencies or config.
- Publish the built static output, not the dev project, and keep secrets and local-only files out of the folder you hand to Revdoku.