Skip to content

Add Cursor Cloud specific development environment instructions#49

Draft
Simplereally wants to merge 1 commit intomainfrom
cursor/development-environment-setup-124b
Draft

Add Cursor Cloud specific development environment instructions#49
Simplereally wants to merge 1 commit intomainfrom
cursor/development-environment-setup-124b

Conversation

@Simplereally
Copy link
Copy Markdown
Owner

@Simplereally Simplereally commented Mar 16, 2026 •
edited by sourcery-ai bot
Loading

Summary

Adds Cursor Cloud specific development environment instructions to AGENTS.md to help future cloud agents set up and run the development environment correctly.

Changes

  • Added ## Cursor Cloud specific instructions section to AGENTS.md with:
    • Product overview (Bloom Studio SaaS app)
    • Services table (Next.js dev server, Convex backend)
    • Required environment variables for .env.local
    • Key commands for lint, test, type-check, and dev
    • Gotchas discovered during setup (proxy.ts middleware, bun test guard, env restart requirement, etc.)

Verification

  • Tests: 205 test files, 2791 tests — all passing (bun run test)
  • Lint: Clean (bun run lint)
  • Dev server: Starts successfully on port 3000 (bun run dev) — compilation works; page serving requires valid Clerk credentials
Open in Web Open in Cursor 

Summary by Sourcery

Documentation:

  • Add Cursor Cloud-focused development environment section to AGENTS.md, covering product context, services, required environment variables, common commands, and setup gotchas.

@cursoragent @Simplereally
Add Cursor Cloud specific instructions to AGENTS.md
353c6e9 
- Document required services (Next.js dev server, Convex backend)
- Document required environment variables for .env.local
- Document key commands (lint, test, typecheck, dev)
- Document gotchas (proxy.ts middleware, bun test guard, env restart)

Co-authored-by: Simplereally <[email protected]>
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Mar 16, 2026

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

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
bloomstudio Ignored Ignored Open in v0 Mar 16, 2026 1:15pm

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Draft detected.

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 53074646-ca84-475c-8731-13811dc801c2

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
  • Post copyable unit tests in a comment
  • Commit unit tests in branch cursor/development-environment-setup-124b
📝 Coding Plan
  • Generate coding plan for human review comments

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

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

Tip

CodeRabbit can use your project's `biome` configuration to improve the quality of JS/TS/CSS/JSON code reviews.

Add a configuration file to your project to customize how CodeRabbit runs biome.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Mar 16, 2026 •
edited
Loading

Reviewer's Guide

Adds a new 'Cursor Cloud specific instructions' section to AGENTS.md that documents how to set up and run the Bloom Studio dev environment (services, env vars, commands, and common gotchas) when working in Cursor Cloud.

Flow diagram for Bloom Studio dev environment setup and gotchas in Cursor Cloud

flowchart TD
  Start["Start in Cursor Cloud workspace"] --> CloneRepo["Open/clone Bloom Studio repo"]
  CloneRepo --> CreateEnv["Create .env.local at repo root"]

  subgraph EnvVars["Populate .env.local"]
    Env1["Set NEXT_PUBLIC_CONVEX_URL"]
    Env2["Set NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY"]
    Env3["Set CLERK_SECRET_KEY"]
    Env4["Optionally set NEXT_PUBLIC_APP_URL (default http://localhost:3000)"]
  end

  CreateEnv --> Env1
  Env1 --> Env2 --> Env3 --> Env4
  Env4 --> StartConvex["Run bunx convex dev (generates convex/_generated/)"]
  StartConvex --> StartNext["Run bun run dev (Next.js dev server)"]

  StartNext --> CheckError["Visit app URL in browser"]
  CheckError --> NoError["Pages load without 500 errors"]
  CheckError --> HasError["Pages return 500 from Clerk middleware"]

  HasError --> FixEnv["Fix Clerk keys in .env.local"]
  FixEnv --> RestartDev["Restart dev server after env change"]
  RestartDev --> CheckError

  NoError --> DevLoop["Development loop: bun run lint, bun run test, bun run typecheck"]

  subgraph Gotchas["Gotchas"]
    G1["Middleware file is proxy.ts, auto-discovered by @clerk/nextjs"]
    G2["Do not run bun test directly, use bun run test"]
    G3[".env* files are gitignored; must create .env.local manually"]
    G4["Convex types require convex/_generated/ from bunx convex dev"]
  end

  StartNext -. reference .-> G1
  DevLoop -. reference .-> G2
  CreateEnv -. reference .-> G3
  StartConvex -. reference .-> G4
Loading

File-Level Changes

Change Details Files
Document Cursor Cloud-specific development environment setup and workflows for Bloom Studio.
  • Introduce a dedicated section describing the Bloom Studio stack and its main services (Next.js dev server and Convex backend) with how-to-run notes.
  • List required environment variables for .env.local, including Convex and Clerk keys, and explain the failure modes when they are missing or invalid.
  • Add a quick reference for key bun-based commands for linting, testing, type-checking, and running the dev server.
  • Capture setup gotchas around Clerk middleware in proxy.ts, proper usage of bun run test, env file gitignore behavior and restart requirements, and Convex-generated types directory.
 AGENTS.md
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Simplereally @cursoragent