Base44 Lets You Connect AI Assistants to Any Workspace
Base44Base44 now lets users connect ChatGPT, Claude, Cursor, or the Base44 CLI to any workspace they belong to, not just their personal one. During setup, users choose which workspace the connection targets, and every action from that AI assistant runs inside that workspace's boundaries. Workspace membership is continuously re-checked on every request and token refresh, and SSO-enforced workspaces remain protected — removing a member or rotating SSO configuration instantly disconnects associated connections.
Key Takeaways
- AI assistant connections (ChatGPT, Claude, Cursor, Base44 CLI) can now target any workspace the user belongs to, not just their personal one.
- Users explicitly select the target workspace during the connection setup flow.
- Workspace membership is re-validated continuously — on every request and token refresh, not just at setup.
- SSO-enforced workspaces remain protected: removing a member or rotating SSO config disconnects associated AI connections instantly.
- The update primarily benefits teams collaborating in shared or enterprise workspaces who also use external AI coding tools.
- It extends Base44's existing MCP-based connection system for ChatGPT, Claude, and Cursor rather than introducing a new integration mechanism.
Bringing AI Assistants Into Team Workspaces
Base44 supports connecting external AI tools — ChatGPT, Claude, Cursor, and its own CLI — directly to a Base44 account so those tools can create, edit, and manage apps on the user's behalf. Until now, those connections were tied to a user's personal workspace only. Base44 has expanded this so a connection can target any workspace the user is a member of, including shared team and enterprise workspaces.
How the Setup Works
During the connection setup flow, users now explicitly choose which workspace the AI assistant should operate in. Every subsequent action taken through that connection — creating an app, editing data, running a workflow — is scoped to that chosen workspace, rather than defaulting to the user's individual space.
Security Stays Intact
Because these connections can now reach team and enterprise workspaces, Base44 built continuous validation into the flow: workspace membership is re-checked on every request and every token refresh, not just at initial setup. For workspaces enforcing single sign-on, that protection carries over fully — if a member is removed from the workspace or the SSO configuration's credentials are rotated, any AI assistant connections tied to that membership are disconnected immediately, with no lingering access.
Why It Matters
This closes a real gap for teams that collaborate inside shared Base44 workspaces but also rely on tools like Claude or Cursor in their individual workflows. Rather than being limited to personal-workspace-only automation, developers and builders can now point their AI coding assistants directly at the team or enterprise workspace where the actual project lives — while Base44 keeps access tightly bound to active, verified membership.