Skip to content

Document Cursor Cloud dev environment setup in AGENTS.md#45

Draft
Sancus wants to merge 1 commit into
mainfrom
cursor/cloud-env-setup
Draft

Document Cursor Cloud dev environment setup in AGENTS.md#45
Sancus wants to merge 1 commit into
mainfrom
cursor/cloud-env-setup

Conversation

@Sancus

@Sancus Sancus commented Jun 18, 2026

Copy link
Copy Markdown
Member

What changed?

Adds a ## Cursor Cloud specific instructions section to AGENTS.md capturing how to set up and run the Stormbox dev environment on a Cursor Cloud VM (as opposed to the human thundermail-dev devcontainer flow). It documents:

  • Running npm/node/npx/Playwright directly on the VM, with only the thunderbird-accounts stack (Keycloak + Stalwart) in docker-in-docker.
  • The Node 24 / PATH shadowing gotcha (/exec-daemon/node is v22) and how to prepend the nvm v24 bin dir.
  • The VITE_* env vars that must be exported in the shell before npm run dev (Vite reads process.env directly in vite.config.js, not .env.development).
  • The 172.17.0.1 stack host resolution (/.dockerenv), Docker 29 daemon caveats (fuse-overlayfs + disabled containerd-snapshotter + iptables-legacy), the self-signed-cert SharedWorker fetch gotcha, and the Stalwart OIDC introspection negative-cache.
  • The full mail-stack bring-up sequence and dev login (admin@example.org / admin).

This change is documentation only. It was agent-written and verified by an AI agent during a full environment setup.

Why?

Future Cursor Cloud agents start from a snapshot with the startup update script already run. These notes let them start services and run the app/tests without rediscovering the non-obvious Cloud-specific caveats.

Limitations and Notes

  • Docs-only change; no application code touched.
  • The startup update script (submodule init, nvm install 24, npm ci, Playwright browsers) is configured separately via the Cloud environment setup, not in this PR.

Applicable Issues

N/A — development environment documentation.

Screenshots

Hello-world verification: logged in as admin@example.org via Keycloak OIDC and viewed the seeded inbox with a message body rendered.

stormbox_login_inbox_demo.mp4

Stormbox inbox with a message open

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

Add a Cursor Cloud specific instructions section covering Node 24 via
nvm, the required VITE_* proxy env vars, the docker-in-docker mail stack
bring-up sequence, and the self-signed-cert SharedWorker gotcha.

Co-authored-by: H <Sancus@users.noreply.github.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.

2 participants