I've been deep in a project to standardize our dev environments and provisioning across a few teams, and naturally my CRM brain went to, "Could we treat Windsurf configurations like infrastructure?" We already use Terraform for cloud resources and Pulumi for some app-level stuff, so it seems logical.
I'm curious if anyone has experimented with managing Windsurf—think workspaces, extensions, maybe even some of those nifty AI prompt configurations—as code via Terraform or Pulumi. I've seen providers for VS Code, but Windsurf feels like its own beast with the baked-in AI and workflow layers.
Specifically, I'm wondering about:
- Is there a way to codify the setup so a new team member gets an identical, pre-configured Windsurf environment on day one?
- Any gotchas around the AI agent configurations or custom commands? Those seem like they'd be more stateful.
- Did you run into issues with extensions or settings that just don't play nice with a declarative approach?
I'm picturing this as a killer combo for RevOps engineers who live in their CRM but also need to script and automate heavily. Would love to hear if anyone's been down this road or if it's still mostly a manual setup process.
I've tried the codify approach with Pulumi for another dev tool. It breaks the moment a user tweaks a setting manually. The config drifts and your IaC is now a lie.
You mentioned AI agent configs and custom commands being stateful. That's the core flaw. These are user-specific workflows, not infrastructure. Trying to force them into Terraform creates more overhead than it saves.
For extensions, you'll hit the same issues as VS Code - some have activation scripts or licenses that don't survive a declarative deploy. You're better off with a documented setup script and accepting some manual config.
If it's not a retention curve, I don't care.
Interesting! I'd love to see a solution here too, though I'm new to this side of things.
The idea of having a new team member get an identical environment from day one sounds perfect. In my old CRM role, onboarding was always a mess of "install this, then click that." If you could codify the core workspace setup for Windsurf, it would save so much time.
Do you think a simpler script to set up the basics first, then let folks tweak the AI bits manually, could be a middle ground? That way you get consistency where it matters.