Start from the app editor
The quickest way to connect is to let the app editor write the prompt for you. The prompt contains everything your agent needs to connect to this app’s sandbox and start working. This option isn’t offered for mobile apps or apps with unmanaged source code. To send an app to your coding agent:- Open the app in the Base44 app editor.
- Click More actions (the three dots next to Publish, in the top right corner), then click Send to Coding Agent.
- Choose a local CLI agent or a web chat.
- Paste the prompt into your agent.
Connect a local agent with the CLI
Use the CLI for an agent that runs on your machine, such as Claude Code, Cursor, or Codex, and for your own scripts. To connect with the CLI:-
Install the CLI. It requires Node.js 20.19.0 or higher.
-
Sign in. This starts a session with the
sandbox:writepermission your agent needs to change files. -
Copy the app ID from the app editor URL:
https://app.base44.com/apps/<app_id>/editor. -
Check the connection by listing the app’s files. Pass
--app-idon every command, or set theBASE44_APP_IDenvironment variable once instead. -
Give your agent this app’s README, which explains how to work in the sandbox with the CLI. It’s public and needs no sign-in.
Connect an agent over MCP
Use the Base44 MCP server for an assistant that connects over MCP, including web chats that can’t run a CLI. To connect over MCP:-
Add the server to your AI tool’s MCP configuration. In Claude Code, run
claude mcp add --transport http base44 https://app.base44.com/mcpinstead. -
Sign in to Base44 when your tool prompts you. In Claude Code, run
/mcpto start it. - Approve sandbox access at the consent step. Without it, your assistant can read the app but can’t change it.
After you connect
Once connected, your agent works through the sandbox commands or MCP tools listed in the cloud sandbox overview. It can list, search, and read the app’s files, change them, and run shell commands in the app’s environment, such as installing a package, running the build, or deleting a file. Each file change is committed as soon as it’s made, so it shows up in the app editor and its live preview right away. Publishing the app is still a separate step. To check that a change compiles, ask your agent to run the build or the type check in the sandbox, for examplenpm run build or npx tsc --noEmit. The development server writes its log to /tmp/vite.log inside the sandbox, so your agent can read compile errors from there as well.
Before a risky set of changes, ask your agent to create a checkpoint. If something goes wrong, restore it from the app editor’s version history.
See also
- Cloud sandbox: How the sandbox works, how changes persist, and the limits that apply
- Base44 MCP server: Connect an AI assistant to your Base44 account
- CLI Overview: Install and use the Base44 CLI
- Build with AI: Create a new backend project on your machine with your coding agent
- Skills: Teach AI coding agents how to work with Base44 projects