# Activation status

The new `knowledge_workspace` database is configured in the selected Chrome account's **Vercel: ahmed's projects** organization. Because this organization disables new projects, setup created a **schema-only `knowledge-workspace` branch** inside `neon-blue-xylophone` (`bold-king-26717419`). The branch ID is `br-red-unit-a21710wa`; it contains no copied parent data. Setup does not modify the original main branch's data or compute.

The Drizzle migration is applied: `resources`, `workspaces`, and `agent_sessions`, including owner indexes and the full-text search index. Neon Auth is enabled for `knowledge_workspace`, with `http://127.0.0.1:5173` trusted for local development. The branch compute is fixed at **0.25 CU**, with five-minute idle suspension. No plan upgrade was made; account usage allowances still apply.

Pooled/direct database connections and the auth endpoint are saved in the private `.env.local` with certificate verification enabled. Cookie and agent secrets are retained. The CLI profile still belongs to a different account; CLI sign-in is unnecessary to run the configured app. Sign into the selected account before future CLI infrastructure changes.

Set these server variables:

| Variable | Purpose |
| --- | --- |
| `DATABASE_URL` | Pooled Neon application connection |
| `DATABASE_URL_UNPOOLED` | Direct connection for Drizzle migrations |
| `NEON_AUTH_BASE_URL` | New branch's managed auth URL |
| `NEON_AUTH_COOKIE_SECRET` | Generated by `setup:env` |
| `AGENT_TOKEN_SECRET` | Generated by `setup:env` |
| `APP_ORIGIN` | App origin, including protocol; localhost by default |

The local app has been restarted with these variables. Create your app account or sign in at `/auth/sign-in`. The workspace requires a server-verified login. Existing Neon resources load on sign-in and later changes save automatically. Browser caches are scoped to each account. Add the production origin to managed auth's trusted domains when deploying. The archive excludes credentials, so another checkout requires its own private environment configuration.

The library has direct Sign in actions in its header, sidebar, and browser-library notice. Account errors are shown explicitly. The requested app user was created through Neon Auth's console. Use **Set or reset password** on the sign-in page to request a secure email link, then choose your password yourself. The app includes `/auth/reset-password` for that link. Password setup and authenticated sign-in still require the account holder; no password was generated or stored by setup.