sandywp add [name] Create a sandbox, follow its provisioning stages, and print a one-time login URL.
Your WordPress workflow, one global install away
Create sandboxes, deploy plugins, push local sites, SSH in, mount files, and clean up — without leaving the terminal you build in.
Trusted by
Small surface, whole workflow
Nine focused command groups cover the loop from first sandbox to final cleanup.
sandywp deploy <name> <plugin.zip> Upload a plugin ZIP, then install and activate it on a sandbox.
sandywp push Mirror the local WordPress install you are in database and wp-content to SandyWP.
sandywp ssh <name> [--cmd] Open a shell inside a sandbox, or run one command and return.
sandywp mount <name> Mount a sandbox's WordPress files locally at ~/SandyWP/<name>.
sandywp login <name> Print a one-time wp-admin login URL, with no password to copy.
sandywp list · status See your sandboxes, account plan, active usage, and remaining capacity.
sandywp unmount · mounts Inspect local mounts, flag stale ones, and cleanly unmount one or all.
sandywp delete <name> Delete a sandbox by slug when the work is done.
Need every flag and requirement? Read the complete CLI reference
Your local install, on a real URL
Run sandywp push from inside a local WordPress install. SandyWP packages its
database and wp-content, restores both into a sandbox, and keeps later pushes
linked to the same URL.
- Push a local install into a new or linked sandbox.
- Mount live sandbox files at
~/SandyWP/<name>. - Edit in your IDE while the public site stays online.
Log in once, from the browser
No API key scavenger hunt. Approve the device, then get back to the terminal.
- 01
Start browser login
Run sandywp auth login. It opens SandyWP so you can sign in normally and approve this device.
- 02
Keep the token local
The personal API token is saved to ~/.sandywp/config.json with restrictive file permissions.
- 03
Revoke whenever you like
Run sandywp auth logout or remove the token from account settings to cut off access.
What terminal people ask
Do I need to install anything?
Install the CLI globally with npm, then run sandywp from any directory. It requires Node.js 18 or newer. SSH uses the OpenSSH already included with macOS and Linux; mounting also requires rclone and a FUSE provider.
Can I use it in CI?
Yes. Authenticate headlessly with sandywp auth login --token and use the same scriptable commands. Commands such as add and deploy also expose flags for non-interactive workflows.
Can AI coding agents use the CLI?
Yes. Any agent that can run shell commands can use the CLI to create sites, deploy plugin ZIPs, use WP-CLI over SSH, mount files, and clean up sandboxes.
Does ssh open a real shell?
Yes it opens a shell inside the WordPress sandbox, with WP-CLI available. Pass --cmd to run one command and exit instead.
Which plans include the CLI?
The CLI is available on every paid SandyWP plan. Your normal plan limits still determine how many sandboxes can be active at once.
Your next site is one command away.
Start with a plan, approve your terminal once, then create real WordPress sandboxes on demand.
$ sandywp add