docs: cloud agent dev environment bootstrap notes#83
Conversation
Co-authored-by: Cole Collins <DealPatrol@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
There was a problem hiding this comment.
Pull request overview
This PR updates AGENTS.md with a new “Cloud agent secrets and local bootstrap” section to help developers boot the app locally in a Cloud Agent environment by documenting required secrets, DB initialization, MCP smoke testing, and key auth/analysis constraints.
Changes:
- Documented required
.env.localsecrets and how to request them via Cursor secrets. - Added a one-time (idempotent) database schema initialization step via
/api/setup/init-db. - Documented MCP structural smoke test usage and clarified limitations around auth/analysis execution.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - Copy `.env.example` to `.env.local` and fill in secrets — `.env.local` is gitignored and is **not** injected automatically by the VM; request `DATABASE_URL`, `GITHUB_CLIENT_SECRET`, and an AI credential (`AI_GATEWAY_API_KEY` or `ANTHROPIC_API_KEY`) via Cursor secrets if missing. | ||
| - One-time schema init: `curl http://localhost:3000/api/setup/init-db` (idempotent; safe to re-run). | ||
| - `pnpm mcp:test` runs a structural MCP smoke test (no live GitHub/AI credentials required). | ||
| - Cookie auth bypass gets you past `/dashboard/*` middleware, but API routes still validate the token against GitHub or a matching `user_auth` row. Analysis detail pages return 404 when the analysis is not owned by the signed-in user. |
Adds a short "Cloud agent secrets and local bootstrap" section to
AGENTS.mddocumenting:.env.local(DATABASE_URL,GITHUB_CLIENT_SECRET, AI credentials)/api/setup/init-dbPart of development environment setup for Cloud Agents.