Set up Cursor Cloud dev environment (web + Android toolchain)

[t3dotgg]

Summary

Sets up the Cursor Cloud development environment for T3 Code and records durable, non-obvious notes for future Cursor agents.

• Web/server toolchain: Node 24.13.1 (nvm, matches engines.node: ^24.13.1), the global vp (Vite+) CLI + bundled pnpm, wired into login shells; deps installed via vp i.
• Cursor-specific notes now live in .cursor/rules/cursor-cloud.mdc (not the shared AGENTS.md), since T3 Code is developed in many editors — AGENTS.md no longer carries a Cursor Cloud section.
• Android toolchain for apps/mobile: OpenJDK 17, Android SDK (platforms;android-36, build-tools;36.0.0, platform-tools, ndk;27.1.12297006, cmake;3.22.1), env wired into login shells; expo prebuild + Gradle verified.

Repo changes here are docs-only (AGENTS.md, .cursor/rules/cursor-cloud.mdc). Toolchain installs live in the VM environment; the startup update script stays minimal (vp i).

Verification

Web/server:

• vp run typecheck — passes (0 errors).
• vp check — passes (0 errors; formatter clean).
• vp test — 4473 passed / 2 pre-existing flakes, unrelated to setup.
• End-to-end: paired the browser, added a project, and had the Claude agent create a file and reply DONE.

Android:

• expo prebuild --platform android generates the native project successfully.
• Toolchain proven end-to-end: ./gradlew :react-native-worklets:assembleDebug → BUILD SUCCESSFUL, compiling Kotlin + C++ (NDK/CMake) into an AAR + 18 .so libs for arm64-v8a.
• Full-app :app:assembleDebug is blocked by a pre-existing app-level issue (not the environment): patches/react-native-screens@4.25.2.patch adds new codegen props (subtitle, largeSubtitle, navigationItemStyle, headerCenterBarButtonItems, headerToolbarItems) with no Android Kotlin setters, so :react-native-screens:compileDebugKotlin fails. The mobile README documents only iOS for local builds and routes Android through EAS. No emulator is possible in this VM (no /dev/kvm).

Hello-world demo (Claude agent creating a file via T3 Code UI)

t3code_claude_agent_hello_world.mp4

Android toolchain evidence

android_toolchain_summary.txt

_{To show artifacts inline, enable in settings.}

  

Note

Add Cursor Cloud dev environment rules for web and Android toolchain

Adds cursor-cloud.mdc, a Cursor agent rules file documenting the development environment setup for Cursor Cloud.

• Covers Node 24 (via nvm), vp CLI usage, and formatter/lint caveats for the web app
• Documents the dev server scripts, port behavior, and pairing/provider CLI flow
• Captures Android native build requirements: JDK 17, Android SDK/NDK versions, prebuild/build commands, emulator limitations, and a known app-level blocker
• Notes known flaky tests to avoid false alarm investigations

^{Macroscope summarized cc99928.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 53089270-1cf1-43f6-b296-29dbd9c58c3f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/setup-dev-environment-a566

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

🟡 Medium rules/cursor-cloud.mdc:3

alwaysApply: true injects these Cursor Cloud–specific environment assumptions into every chat session for every clone of the repo, not just Cursor Cloud. Local Cursor users/agents will be told that Node 24, the Android SDK/NDK, and an unauthenticated pairing server are pre-provisioned, which is false outside the Cloud VM and causes agents to skip local setup steps. The file description already scopes it to Cursor Cloud, so this should be opt-in — set alwaysApply: false (or use globs/description-based matching) so the rule only attaches when explicitly relevant.

Suggested change

	alwaysApply: true
	alwaysApply: false

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @.cursor/rules/cursor-cloud.mdc around line 3:

`alwaysApply: true` injects these Cursor Cloud–specific environment assumptions into every chat session for every clone of the repo, not just Cursor Cloud. Local Cursor users/agents will be told that Node 24, the Android SDK/NDK, and an unauthenticated pairing server are pre-provisioned, which is false outside the Cloud VM and causes agents to skip local setup steps. The file description already scopes it to Cursor Cloud, so this should be opt-in — set `alwaysApply: false` (or use `globs`/`description`-based matching) so the rule only attaches when explicitly relevant.

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. Documentation-only change adding Cursor Cloud environment setup notes. However, an unresolved comment correctly identifies that alwaysApply: true will inject Cloud-specific assumptions to all Cursor users, potentially misleading local developers. This configuration concern should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}