Skip to content

Set up Cursor Cloud development environment #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
rdtiv wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Set up Cursor Cloud development environment #14

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
107452d
Add AGENTS.md with Cursor Cloud environment instructions
cursoragent Aug 22, 2026
f2ccdd5
Document pulling OpenAI key from Vercel project in AGENTS.md
cursoragent Aug 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# AGENTS.md

## Cursor Cloud specific instructions

ChatProb is a single Next.js 13 (pages router) app that teaches how an LLM samples
text. There is one product and one deployable service.

### Service: ChatProb web app
- Dev server: `npm run dev` (Next.js on http://localhost:3000). Runtime is Node.js,
not Edge — the `/api/chat` route needs the Node runtime so OpenAI logprobs survive.
- Lint: `npm run lint` (passes with only pre-existing `react-hooks/exhaustive-deps`
warnings in `components/Message.js`).
- Unit tests: `node --test "lib/*.test.js"` (pure `lib/` modules, no network calls).
- Build (prod): `npm run build`; not needed for development.

### OpenAI key requirement (important, non-obvious)
- The chat feature calls the OpenAI Chat Completions API. Without `OPENAI_API_KEY`
set, the UI loads fine but `POST /api/chat` returns `{"error":"OPENAI_API_KEY is
not set"}` and no reply/heatmap is produced.
- Getting a key: the `rdtiv/chatprob` Vercel project already holds `OPENAI_API_KEY`
(and `OPENAI_MODEL`) as environment variables, including a Development scope. Pull
them locally with the Vercel CLI using the `Vercel_Token` secret injected into the
agent environment:
```bash
export VERCEL_TOKEN="$Vercel_Token"
npx -y vercel@latest link --yes --project chatprob --token "$VERCEL_TOKEN"
npx -y vercel@latest env pull .env.local --environment=development --yes --token "$VERCEL_TOKEN"
```
This writes a real `OPENAI_API_KEY` into `.env.local` (gitignored — never commit it).
- Do NOT route this app through the Vercel AI Gateway or the Edge runtime: both drop
the token `logprobs`/`top_logprobs` that the entire UI is built to visualize. Use a
direct OpenAI key with the Node runtime.
- Optional overrides: `OPENAI_MODEL` (default `gpt-4o-mini`) must support Chat
Completions `logprobs` and `n`; `OPENAI_BASE_URL` (default OpenAI). Env vars are read
at request time in `pages/api/chat.js`, but Next.js only loads `.env`/`.env.local`
at server start — restart `npm run dev` after changing them.

### Manual scripts (do not run in CI)
- `scripts/stream-spike.mjs` and `scripts/temp-gate-check.mjs` hit the live OpenAI API
and are manual gates only. They require `OPENAI_API_KEY`.