Allow Anonymous (Unauthenticated) Agent Conversations in Production

TL;DR
Base44 Agents work in Preview but fail in published apps for unauthenticated users (401: User must be authenticated). This blocks using Agents as public website chatbots. Please support anonymous agent conversations in production.

Problem
In Preview mode, agents run correctly because users are implicitly authenticated.
In published apps, unauthenticated visitors cannot create agent conversations, causing Agents to fail entirely on public websites.

This mismatch between Preview and Production is confusing and prevents a very common use case.

Why This Matters
Many teams want to use Base44 Agents as:

• Public website chatbots (Intercom-style)

• Lead qualification assistants

• Scheduling assistants (Google Calendar booking)

Requiring login before chat severely hurts UX and conversion. Authentication is typically desired after interest is established.

Requested Feature
Add support for anonymous agent conversations in published apps, with clear controls such as:

• App- or agent-level toggle: “Allow unauthenticated conversations”

• Permission scoping for anonymous users (e.g., tool access, entity writes)

• Clear documentation of Preview vs Production behavior

Impact
This would:

• Unlock Agents for real public website use

• Improve conversion rates for customers

• Reduce Preview → Production confusion and support load

• Make Base44 Agents competitive with Intercom/Drift-style chatbots