Base44: User Entity Now Available in Local Dev Server

Local Dev Server Now Supports the User Entity

Base44's base44 dev command has long provided a fast local feedback loop for backend development — running functions locally with hot reload, using an in-memory entity database, and forwarding unsupported operations (like OAuth and AI generation) to the production deployment. One notable gap, however, was the User entity: developers building user-aware logic had to deploy to production to test it.

That gap is now closed. The local dev server seeds a User record automatically on startup, enabling full local testing of user-scoped features.

How It Works

When the dev server starts, it reads the developer's authenticated CLI credentials and seeds a single User record from them. This record is immediately available for any backend function or entity query that touches the User entity or calls me.

The behavior is deliberately constrained to mirror production semantics:

• Read operations (getMe, queries on User) work exactly as they would in production.
• Update operations on the seeded user record work as in production.
• Create and delete operations are silently ignored — consistent with how the production User entity behaves, where users are provisioned through authentication flows rather than direct CRUD.

Why This Matters

Before this change, any backend function that referenced User data — personalizing responses, checking roles, reading preferences — required a full deployment cycle to test. Now, developers can build and iterate on user-aware features entirely locally. The seeded user record, drawn from real CLI credentials, provides realistic test data without any manual setup.