docs: add Cursor Cloud environment setup notes to AGENTS.md - #3631
Draft
mitul-s wants to merge 1 commit into
Draft
docs: add Cursor Cloud environment setup notes to AGENTS.md#3631mitul-s wants to merge 1 commit into
mitul-s wants to merge 1 commit into
Conversation
|
Contributor
Contributor
Sim WorldSimulated world deterministic testing for races. Traces 🟠 world-sim scenario book — 1 fail of 41 total
Full trace: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Sets up the Cloud Agent development environment for this repo and records the non-obvious startup/run caveats discovered during setup in a new
## Cursor Cloud specific instructionssection ofAGENTS.md.No package code changed — this PR only adds documentation to
AGENTS.md. The actual environment configuration lives in the Cloud Agent startup update script (pnpm install --frozen-lockfile) and the VM snapshot (which now ships a Ruststabletoolchain +wasm32-unknown-unknowntarget so@workflow/swc-plugincompiles).Key learnings captured for future agents:
pnpm build(repo root) is required before running/e2e-testing any workbench app.@workflow/swc-plugin) whoseCargo.tomlneedsedition2024(Rust/Cargo ≥ 1.85); the base image's default Rust (1.83) is too old, so the snapshot now defaults to Rust stable ≥ 1.97.world-local— no Postgres/Docker/Vercel needed for local dev or the HTTP e2e suite.workbench/nextjs-turbopackis the primary runnable app for manual/e2e testing, with a quick HTTP smoke-test recipe.How did you test your changes?
Verified the full local dev loop end-to-end:
pnpm install --frozen-lockfilepnpm build(28 packages, incl. Rust→WASM SWC plugin)pnpm lint(Biome)packages/world-localvitestWORKFLOW_PUBLIC_MANIFEST=1 pnpm devinworkbench/nextjs-turbopackDEPLOYMENT_URL=http://localhost:3000 APP_NAME=nextjs-turbopack pnpm vitest run packages/core/e2e/e2e.test.ts -t "sleeping"POST /api/workflows/start {simple,[42]}→ awaitresult: 57simpleworkflow from the browser UIBrowser walkthrough (select + run
simpleworkflow, completes with result 57):nextjs_turbopack_simple_workflow_run.mp4
simple workflow completed in the UI with result 57
PR Checklist - Required to merge
pnpm changeset— docs-only change (AGENTS.md); usepnpm changeset --emptyif required by CI@vercel/workflowwhen readyTo show artifacts inline, enable in settings.