Skip to content

docs: cloud agent dev environment bootstrap notes #83

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
DealPatrol wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −0
Draft

docs: cloud agent dev environment bootstrap notes #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,11 @@ pnpm build # production build (requires valid DATABASE_URL at build time)
- `pnpm install` may show a warning about ignored build scripts for `sharp` and `unrs-resolver`. These do not affect development.
- The GitHub OAuth env vars in this repo use `GITHUB_CLIENT_ID` / `GITHUB_CLIENT_SECRET` (not `GITHUB_ID` / `GITHUB_SECRET`). If secrets are injected under different names, map them in `.env.local`.
- `NEXT_PUBLIC_APP_URL` must be set to the local dev server URL (default port 3000) for local OAuth callback redirects to work.

### Cloud agent secrets and local bootstrap

- 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.
- Running an analysis (`POST /api/analyses/[id]/run`) requires a configured AI provider; without it the UI shows "AI is not configured".
Loading