testing-eve-web

name	testing-eve-web
description	Run and test the Eve web chat app (apps/eve) end-to-end locally — dev server setup, Vercel env, sending messages, model selector, and Eve session API smoke tests. Use when verifying UI or agent-behavior changes in apps/eve.

Testing the Eve web chat (apps/eve)

Setup

1. Deps: npm install at the repo root.
2. Env: the app needs Vercel-provided env (Neon DATABASE_URL, Blob, OIDC for sandboxes). Pull it from the correct project (root directory is apps/eve):

   cd apps/eve
   npx vercel link --yes --project personal-agent --scope ${SENTRY_ORG} --token "$VERCEL_TOKEN"
   npx vercel env pull .env.local --yes --token "$VERCEL_TOKEN"
   

3. Dev server (detached, survives shell exit — plain nohup may not):

   cd apps/eve && setsid nohup npm run dev > /tmp/dev.log 2>&1 < /dev/null &
   

   App at http://localhost:3000. Check /tmp/dev.log for OIDC/DB errors; if OIDC expired, re-run vercel env pull.
4. Typecheck: cd apps/eve && npm run typecheck.

Smoke-testing agent behavior via the Eve session API

/eve/v1/** is served on the same origin: withEve (next.config.ts) mounts the agent service into the Next.js dev server. It only 404s while the embedded agent backend is still booting — wait for in before curling: