Registration flow

[KIvanow]

Testing steps:

Here's the full local testing setup:

1. Start Postgres (test instance on port 5433)
   docker compose -f docker-compose.test.yml up -d postgres

2. Start the entitlement service (port 3002)
   cd proprietary/entitlement

Create .env with:

ENTITLEMENT_DATABASE_URL="postgresql://betterdb:devpassword@localhost:5433/betterdb"

RESEND_API_KEY=re_your_key_here

Run migrations (first time only)

ENTITLEMENT_DATABASE_URL="postgresql://betterdb:devpassword@localhost:5433/betterdb" pnpm prisma:migrate
pnpm prisma:generate

PORT=3002 pnpm dev

3. Start the monitor (API on 3001, web on 5173)

From repo root, with these in .env or inline:

VITE_REGISTRATION_URL=http://localhost:3002/v1/registrations

ENTITLEMENT_URL=http://localhost:3002/v1/entitlements

Unset any existing license key

unset BETTERDB_LICENSE_KEY

ENTITLEMENT_URL=http://localhost:3002/v1/entitlements pnpm dev

4. Test the flow
   Open http://localhost:5173 → Settings → License
   Register with an email
   Check entitlement service console for the license key (if no Resend key) or check email
   Paste the key in "Already have a license key?" → Activate
   Should upgrade to Enterprise tier
5. Reset test data (if needed)

List what's there

docker exec betterdb-test-postgres psql -U betterdb -d betterdb -c "SELECT id, key FROM licenses;"

Delete a specific registration

docker exec betterdb-test-postgres psql -U betterdb -d betterdb -c
"DELETE FROM licenses WHERE customer_id = ''; DELETE FROM customers WHERE email = '';"

---

Note

High Risk
Adds a new WebSocket-backed CLI that can execute database commands (including an opt-in unsafe mode) and introduces new registration/email + runtime license activation paths, expanding the system’s attack surface and affecting licensing state persistence.

Overview
Adds an integrated Valkey/Redis CLI panel backed by a new API WebSocket endpoint (/cli/ws). The backend introduces CliGateway + CliService with command parsing, rate limiting, timeouts, output truncation/formatting, and shared safe/blocked command enforcement (with BETTERDB_UNSAFE_CLI=true to allow writes), plus a dedicated BetterDB-CLI Valkey client path in the database adapters.

Implements a free registration + activation flow for licensing. The web app adds a new Settings License section that can register an email (via VITE_REGISTRATION_URL) and activate a license key via a new POST /license/activate endpoint; the API now persists activated keys to disk and hardens error handling/message extraction, while the entitlement service adds a /v1/registrations endpoint that creates/resends enterprise licenses and sends emails via Resend (plus CORS/env updates and cloud tenant-based entitlement resolution via tenantId).

^{Reviewed by Cursor Bugbot for commit 9e89017. Bugbot is set up for automated code reviews on this repo. Configure here.}

[KIvanow]

@cursor review

[KIvanow]

@cursor review

[jamby77]

Code review

Found 1 issue:

1. Registration fallback URL targets port 3001 (monitor API) instead of port 3002 (entitlement service). When VITE_REGISTRATION_URL is not set, POST /v1/registrations hits the monitor API which has no such route, causing registration to silently fail with a 404. The PR's own testing steps confirm the entitlement service runs on port 3002.

monitor/apps/web/src/api/registration.ts

Lines 1 to 2 in 2e8b23d

	const REGISTRATION_URL = import.meta.env.VITE_REGISTRATION_URL || 'http://localhost:3001/v1/registrations';

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[github-actions]

Thank you for your contribution! Before we can merge this PR, you need to sign our Contributor License Agreement.

To sign, please comment below with:

I have read the CLA Document and I hereby sign the CLA

---

I have read the CLA Document and I hereby sign the CLA

---

2 out of 3 committers have signed the CLA.
✅ (KIvanow)[https://github.com/KIvanow]
✅ (jamby77)[https://github.com/jamby77]
❌ @cursoragent
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[cursor]

Error double-logged on Resend API failure

Low Severity

When the Resend API returns a non-OK response, the error is logged at line 66 with response details, then the thrown Error is immediately caught by the outer catch block at line 72 which logs it again. This produces redundant log entries for every failed email delivery attempt.

 

^{Reviewed by Cursor Bugbot for commit 325259c. Configure here.}

[KIvanow]

Some extra logging is fine

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8a5848d. Configure here.}

[cursor]

Race condition in lazy CLI client initialization

Medium Severity

getCliClient() has a race condition during lazy initialization. The first caller sets this.cliClient synchronously via createValkeyClient() then awaits connect(). A second concurrent caller sees this.cliClient is non-null and returns it immediately — before connect() has resolved. Since the client is created with enableOfflineQueue: false, commands sent on the not-yet-connected client will fail. The same pattern exists in Agent.getCliExecutor().

Additional Locations (1)

• packages/agent/src/agent.ts#L191-L203

 

^{Reviewed by Cursor Bugbot for commit 8a5848d. Configure here.}

[KIvanow]

not from this branch - caused by the updated with master

[jamby77]

Other than that localhost:3001 (API url) does not need to be in CORS, everything else seems fine