Local-directory saving is a different destination from browser storage. It writes the Playground to a user-selected folder and needs folder permission again after refresh.
Active Playground object
Unsaved Playground
- Storage
- temporary memory
- Identity
- no slug yet
- Reload consequence
- refresh closes the site unless saved
- Selected command
- Save to local directory
Command form
Save to local directory
Browser storage creates a saved Playground row and a slug on this device. It does not expose a local folder and it survives refresh in this browser.
Start a fresh Vanilla WordPress Playground. This replaces the current temporary site after confirmation and returns the path to the welcome page.
Preview a WordPress PR with a PR number or full GitHub URL. The resulting preview remains temporary until saved.
Preview a Gutenberg PR, URL, or branch name. This route records the branch source and unlocks save/export actions after build.
Import plugins, themes, or wp-content directories from GitHub. Account connection is required and the access token is not stored after refresh.
Run a Blueprint from a URL after validation. Running a Blueprint can alter files, database content, settings, and the current preview path.
Import .zip uses the native file chooser. The selected archive is validated before the user confirms replacement of files and database.
Rename mutates the active shell title, selected object row, saved identity label, and ledger event. Slugs update only for browser-backed saves.
Delete is destructive for saved browser or local-directory identities. Confirmation removes the saved row and returns the shell to an unsaved temporary Playground.
Stored Playgrounds use Save & Reload. Unsaved Playgrounds use Apply Settings & Reset because the runtime is rebuilt.
The file operation below finishes end to end: select wp-config.php, mark it dirty, save it, update result state, and record a log event.
Blueprint gallery shows a labeled representative subset of the 43 captured blueprints, with current categories, search, selected detail, JSON editor, copy, download, run, and validation states.
Database management remains early access and uses MySQL emulation backed by SQLite.
- Driver
- MySQL emulation backed by SQLite
- Path
- /wordpress/wp-content/database/.ht.sqlite
- Size
- 452 KB
Playground: no boot errors.
WordPress: notice from wp-content/plugins/friends/feed.php:42.
PHP: memory usage steady after last reload.
Export to GitHub uses a session-only account connection, repository target, push progress, and final transfer history entry.
Download as .zip packages current WordPress files, wp-content, blueprint.json, and the SQLite database into a portable archive.
Download only the SQLite database used by the active Playground.
Settings selected: saved sites reload; unsaved sites reset and lose temporary changes.