Set up Cursor Cloud dev environment for RepoAtlas

[ChimdumebiNebolisa]

Summary

Sets up and verifies the development environment for RepoAtlas (single Next.js 14 app) in Cursor Cloud, and documents non-obvious setup caveats for future agents.

• Adds AGENTS.md with a ## Cursor Cloud specific instructions section covering the e2e/dev-server port collision, e2e state contamination, Playwright browser install, and the core smoke-test workflow.
• Update script (VM startup) installs dependencies and the Chromium browser needed for Playwright:
  • npm ci
  • npx playwright install --with-deps chromium

No application code was changed.

Verification

Check	Command	Result
Install	npm ci	pass (610 packages)
Lint	npm run lint	pass (no warnings/errors)
Unit tests	npm test	pass (121/121)
Build	npm run build	pass
Dev server	npm run dev	pass (homepage 200)
E2E	PLAYWRIGHT_PORT=3100 npm run test:e2e	pass (32/32)

Core functionality verified end-to-end: analyzed the fixtures/repo-ts fixture via POST /api/analyze, fetched the generated report, exported Markdown, and drove the UI "Try sample Candidate Brief" flow (Candidate Brief + interactive Architecture Map render correctly).

Walkthrough

repoatlas_candidate_brief_demo.mp4

Candidate Brief rendered
Interactive Architecture Map tab

Note: npm run test:e2e reuses an already-running dev server on port 3000 (reuseExistingServer: !CI), which uses a different REPORTS_DIR than the tests expect and causes false failures. Run e2e on an isolated port (PLAYWRIGHT_PORT=3100) when a dev server is running. See AGENTS.md for details.

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

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
repo-atlas	Ready	Preview, Comment	Jul 10, 2026 5:23pm