Skip to content

Set up Cursor Cloud dev environment for Paradise Planner#12

Draft
ether314 wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-f637
Draft

Set up Cursor Cloud dev environment for Paradise Planner#12
ether314 wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-f637

Conversation

@ether314

Copy link
Copy Markdown
Owner

Summary

Sets up the development environment for the Paradise Planner (Vacation Agent) repo so cloud agents can lint, test, build, and run the apps. Documents non-obvious startup caveats in AGENTS.md under ## Cursor Cloud specific instructions.

The only code change is the AGENTS.md addition; the rest is environment setup (Flutter SDK install + dependency installs) captured via the startup update script.

Environment

  • Installed Flutter 3.44.2 / Dart 3.12.2 (matches flutter_app/pubspec.lock) at /opt/flutter, symlinked into /usr/local/bin, web enabled.
  • Update script refreshes deps on startup: flutter pub get (flutter_app/) and npm install (functions/, slack-orchestrator/).

Verification

  • flutter pub get, flutter analyze (only 4 pre-existing info/warning lints), flutter test (12/12 pass)
  • functions + slack-orchestrator npm install + npm run build succeed
  • Backend connectivity: node scripts/test-chat-flow.mjs (Gemini reply OK) and node scripts/test-submit-lead.mjs (HTTP 200)
  • Ran the customer web app (flutter run -d web-server -t lib/main_customer.dart) and completed a hello-world E2E: chatted with the AI concierge, provided trip details + phone, and reached the lead-submission handoff confirmation.

paradise_planner_chat_e2e.mp4

Greeting loaded
Handoff confirmation

Note: the apps talk to the live Firebase project vacation-app-21706 (hardcoded config); no emulator wiring exists, so chat/lead flows need network access to Firebase. Twilio SMS is optional.

Open in Web Open in Cursor 

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