Set up Cursor Cloud dev environment + run/setup caveats

[andrmaz]

Summary

Sets up the development environment for the Cortex monorepo on Cursor Cloud and documents durable, non-obvious startup/run caveats for future agents. Docs-only changes: the Cursor Cloud notes live in a dedicated docs/agents/cursor-cloud.md following the repo's progressive-disclosure pattern, linked from AGENTS.md and docs/agents/README.md.

What was set up

• pnpm install (Node 22, pnpm 9).
• PostgreSQL 16 installed natively (Docker is unavailable in the VM); cortex/cortex/cortex role+db created on :5432.
• Generated the Prisma client and applied the committed migration SQL (9 tables).
• Created a gitignored /workspace/.env with dev DATABASE_URL + JWT_SECRET.

Update script (runs on startup)

pnpm install
DATABASE_URL="postgresql://cortex:cortex@localhost:5432/cortex" pnpm --filter db db:generate

Verification

Check	Result
pnpm check-types	✅ 6/6
pnpm lint	✅ 4/4
pnpm build	✅ 4/4
pnpm test	✅ 74 tests (shared 21, api 53)
@cortex/web dev (3000)	✅ HTTP 200
@cortex/docs dev (3001)	✅ HTTP 200
@cortex/api (4000) end-to-end	✅ MCP query, JWT auth, DB persistence

API hello-world (end-to-end)

POST /mcp returns a governed response; GET /api/me is 401 without a token and 200 with a minted JWT; the provisioned org+user row persists in Postgres.

web app on :3000
docs app on :3001

Note: booting the API end-to-end required temporary, reverted, non-committed tweaks (Prisma 7 @prisma/adapter-pg driver adapter + a TS run-config), because as committed the API cannot be booted by its own scripts. See docs/agents/cursor-cloud.md for details.

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

  

[coderabbitai]

Warning

Review limit reached

@andrmaz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c03db8ad-f84e-4d54-ba4f-19dd54ef27c0

📥 Commits

Reviewing files that changed from the base of the PR and between 379d638 and f1e0629.

📒 Files selected for processing (3)

• AGENTS.md
• docs/agents/README.md
• docs/agents/cursor-cloud.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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