base44-remote-dev Skill for Claude: What It Does and How to Install It
Lets your own coding agent edit and run a Base44 app in Base44's cloud sandbox over MCP.
- Installs
- 9.2K
- on skills.sh
- Stars
- 92
- on GitHub
- Updated
- Nov 2026
- last repo commit
This is Base44's own skill for working on a Base44 app from outside the editor. Claude connects to the app's cloud sandbox over MCP, or through the base44 sandbox command line, then reads files, edits them, runs commands and saves checkpoints. Base44 supplies the sandbox and you supply the agent.
It needs the Base44 MCP server (app.base44.com/mcp) and a Base44 sign-in. Write and shell tools need an extra scope that is not on by default. The folder holds only SKILL.md and bundles no scripts.
Good for
- Base44 builders who want their own coding agent to work on an app
- People who use Claude Code, claude.ai or another MCP client instead of the Base44 chat
- Anyone who wants no local checkout of the app
Install base44-remote-dev
Claude Code
- 1
Copy this prompt.
Install the base44-remote-dev skill in Claude Code. Run this command: /plugin marketplace add base44/skills claude plugin install base44-sandbox@base44-skills Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Pick one skill route, then connect the Base44 MCP server (Claude Code: run the second command, then /mcp, select base44 and Authenticate; a browser opens for the Base44 sign-in). The sandbox plugin installs 13 skills (counted from its plugin.json) and deliberately leaves out base44-cli. A local agent can skip MCP and use npx base44 sandbox after npx base44 login. The claude tab is the in-editor Send to Coding Agent flow, which SKILL.md describes; it does not upload this skill.
From the project README. Source.
What's in the skill
When it loads
Develop a Base44 app remotely from your own coding agent (Claude Code, claude.ai, or any MCP client) by connecting it to the Base44 sandbox. Cloud agents connect over MCP; local agents can connect over MCP or drive the same sandbox with the `base44 sandbox` CLI subcommands (the CLI uses shorter names — e.g. read_file is `sandbox read`, list_directory is `sandbox ls`, run_command is `sandbox run`). Covers connecting/ authenticating, the available sandbox tools (run_command, read_file, write_file, edit_file, grep, list_directory, create_checkpoint, list_user_apps, and the connector tools list_connectors / initiate_connector_connection), the edit→preview→verify loop, how changes persist, builder/external-agent concurrency, the in-editor "Send to Coding Agent" button + onboarding README URLs, and tips like reading the Vite dev-server logs. Triggers on "develop my Base44 app remotely", "connect Claude Code to Base44", "bring my own agent", "edit a Base44 app over MCP", "Base44 sandbox MCP", or "Send to Coding Agent".
Sections in SKILL.md
- 1. Connect the MCP server
- 2. Authenticate
- Scopes
- 3. Pick the app and orient yourself
- 4. Make changes
- 5. Preview and verify (the edit → check loop)
- 6. How your changes persist
- 7. Concurrency: you vs. the Base44 builder
- 8. Guardrails & limits
- Error codes you may see
- 9. Tips & tricks
- 10. Local agents via the base44 sandbox CLI
- 11. Connectors (OAuth integrations)
Key facts
- Repo
- base44/skills
- Installs on skills.sh
- 9,159 (Nov 2, 2026)
- GitHub stars
- 92 for the whole repo (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
- What it includes
- 1 file: SKILL.md. It bundles no scripts
- Status
- Beta, per the README
What it includes
Adds https://app.base44.com/mcp to Claude Code, then you authenticate in /mcp
Other MCP clients work too. Headless clients use the OAuth device flow instead of a browser.
Network ·
Connect the MCP serverLists your Base44 apps so you can pick the appId every tool needs
Network ·
list_user_appsLooks around the sandbox, reads files by line range, searches code
SKILL.md says to start read-only and summarize the structure before editing.
Try: “Using the base44 tools on my app, list the root folder and summarize the structure”
Network ·
list_directory / read_file / grepApplies exact old_text to new_text edits atomically, with a dry_run preview
Preferred over write_file for existing files. Each old_text must be unique unless replace_all is set.
Try: “Change the homepage heading from Welcome to Welcome back. Show me the diff first with dry_run, then apply it.”
Write ·
edit_fileCreates new files; overwriting needs overwrite: true
Write ·
write_fileRuns a bash command in the sandbox for builds, installs or tailing /tmp/vite.log
Needs sandbox:write. Output is capped at about 1 MB.
Runs code ·
run_commandSaves a restore point in the builder's version history
SKILL.md says to call it after each unit of work and always before stopping.
Write ·
create_checkpointReads or sets up OAuth connectors such as Google Calendar or Slack
You must open the authorization link to consent.
Write ·
list_connectors / initiate_connector_connectionEdit, build, read Vite logs, then open the preview URL
Preview URL comes from GET /api/apps/{app_id}/sandbox/preview-url, reachable over MCP with execute_api.
Runs code ·
Preview and verify loopSame tools for local agents: sandbox ls, read, write, edit, run, grep, checkpoint
Run `npx base44 login` first. It resolves the app from --app-id, BASE44_APP_ID or a local .app.jsonc.
Runs code ·
base44 sandbox CLI
From the official docs
Permissions
High risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only modeHow to turn it on
Watch out for
It runs shell commands in your Base44 sandbox
run_command executes any bash command in the app's cloud sandbox (120 second default timeout, 600 maximum). That is Base44's sandbox, not your machine. It needs the sandbox:write scope, which is not granted by default. github.com
Edits are saved and pushed within seconds
Every mutating call schedules an auto-commit after about 5 seconds that pushes to Base44 code storage. Those changes appear in the builder and are included when you publish. Review the diff with dry_run first. github.com
Un-checkpointed work can be wiped
Only checkpoints show in version history. If someone clicks Restore or Revert in the builder, everything after the last checkpoint is discarded. Ask Claude to create a checkpoint when it finishes. github.com
It blocks the Base44 builder while it works
While your agent is using the sandbox tools, the builder chat is blocked with "An external agent is currently working on this app". Do not run two agents on one app. github.com
Connector scopes are replaced, not merged
initiate_connector_connection sets a connector to exactly the scopes passed and re-prompts for consent. Claude should list the current scopes first. You open the authorization link yourself. github.com
Files can be deleted with rm
There is no delete_file tool. SKILL.md says to delete through run_command rm, which needs sandbox:write. The .agents folder is protected from the file tools. github.com
Technical details
| Turning on read-only | apps:read is granted by default, so read_file, grep and list_directory work without sandbox:write. The mutating tools return NOT_AUTHORIZED until you grant it. |
|---|---|
| Talks to | app.base44.com |
| Sign-in and keys | Claude Code signs in to the MCP server with Base44 OAuth (PKCE) in your browser. Headless clients use the OAuth device flow. The CLI route uses your Base44 CLI token. |
| Scopes |
|
Questions
What does the base44-remote-dev skill do?
It shows Claude how to connect to a Base44 app's cloud sandbox and work in it: read and edit files, run commands, check the preview, and save checkpoints. Base44 supplies the sandbox. You supply the coding agent.
How do I install base44-remote-dev?
Use the install box above. In Claude Code, add the sandbox plugin or the skill, then run the MCP command in the box and sign in through /mcp. The simplest start is the Send to Coding Agent button in the Base44 editor, which gives a ready-made prompt.
What is the Base44 MCP server URL?
https://app.base44.com/mcp. SKILL.md registers it in Claude Code with claude mcp add --transport http base44 https://app.base44.com/mcp. It only adds the config. You then authenticate through /mcp.
Why do the write tools say NOT_AUTHORIZED?
Your token is missing the sandbox:write scope, which is not granted by default. SKILL.md says to reconnect and grant sandbox access. Reads work without it.
Does it work in claude.ai?
Yes, SKILL.md describes it. The web route uses the regular claude.ai chat with the Base44 MCP connector, not Claude Code on the web. The editor's Send to Coding Agent button gives a prompt to paste and an Open Claude button.
Can I use it without MCP?
Yes, a local agent can use the base44 sandbox CLI commands instead. You sign in with base44 login. The CLI names are shorter: sandbox read, sandbox ls, sandbox run, sandbox checkpoint and so on.
Is it safe?
It can run shell commands and write files in your app's sandbox, and changes are auto-committed and pushed within about 5 seconds. Read access is separate from write access. Our advice: grant only the read scope until you have reviewed what Claude plans, and make it create a checkpoint at the end.
Which skills go with it?
base44-sandbox covers what to write in the sandbox. base44-sdk covers the SDK calls. The sandbox plugin installs both plus base44-troubleshooter and 9 platform skills.
Is it an official Base44 skill?
It is in Base44's own repo, and the repo's marketplace.json describes the skills as "Official Base44 skills for Claude Code". A comment in the file says it was vendored from base44-dev/apper PR #11608.
Information
updated Nov 2, 2026
- Repository
- base44/skills
- Folder
skills/base44-remote-dev
Sources
Docs, issue trackers and discussions this page is built from.
Show all 4Hide
- base44/skills README · github.com
- base44/skills marketplace.json · github.com
- base44-sandbox plugin.json · github.com
- base44-remote-dev SKILL.md · github.com