829cli
v1.6.0
Published
829 Studios CLI tools — plugin management, SSH, and more
Readme
829
Command-line tools for managing WP Engine installs at scale — plugin management, SSH connections, portal access, user management, and more.
Requirements
- Node.js >= 18 (nodejs.org)
- WP Engine API credentials — username and token from the WP Engine User Portal
- SSH keys configured for WP Engine (docs)
- fzf (optional, required for Tab autocomplete) —
brew install fzf
Installation
npm install -g 829cliFirst-time Setup
1. Configure your API credentials
829 configYou will be prompted for:
- WP Engine API username
- WP Engine API token
- Default batch size (recommended: 20)
- Default parallel jobs (recommended: 20)
Settings are saved to ~/.829.json.
2. Sync your installs and accounts
829 installs sync
829 accounts syncThese fetch all WP Engine installs and accounts from the API and cache them to ~/.829/installs.json and ~/.829/accounts.json. Re-run them any time installs or accounts are added or removed.
3. Enable Tab autocomplete (zsh)
Add the following to your ~/.zshrc:
eval "$(829 completion zsh)"Then reload your shell:
source ~/.zshrcRequires
fzf. Install withbrew install fzf.For bash, use
eval "$(829 completion bash)"in your~/.bashrc.
Commands
829 config Configure API credentials and defaults
829 installs sync Fetch installs from the WP Engine API
829 installs list Browse cached installs
829 ssh [install-id] SSH into a WP Engine install
829 scp [install-id] Push or pull files to/from an install
829 portal [install-id] Open install in the WP Engine portal
829 accounts sync Fetch accounts from the WP Engine API
829 accounts list Browse cached accounts
829 portal user list Show one account's users, or export all accounts (CSV)
829 portal user add Add a user to an account
829 portal user delete Remove a user from an account
829 portal user promote Change a user's role in one account or all accounts
829 plugin scan Scan plugin status across installs
829 plugin activate Activate a plugin across installs
829 plugin deactivate Deactivate a plugin across installs
829 plugin update Update a plugin across installs
829 plugin delete Delete a plugin across installs
829 run Run a shell command across installs via SSH
829 wpt provision Install/update wordpress-tools and provision API keys
829 wpt settings Update wordpress-tools settings across installs
829 wpt repair Fix misnamed wordpress-tools-main plugin folder
829 cookies <sitemap-url> Audit cookies/localStorage/sessionStorage across a site
829 crawl <url> Crawl a site and export a CSV inventory of pages
829 help Show all commands
829 help <command> Show detailed help for a command
829 completion zsh Print zsh completion script
829 completion bash Print bash completion scriptRun 829 help at any time for the full reference, or 829 help <command> for detail on a specific command (e.g. 829 help plugin, 829 help user, 829 help accounts).
File Transfer (scp)
829 scp uploads (push) or downloads (pull) files and folders between your machine and a WP Engine install.
829 scp [install-id] [push|pull] [source] [destination]Every argument is optional — anything you leave off is prompted for. Pass all four to run it in one line, or none for a fully interactive session.
One-liners:
# Upload a file
829 scp asphaltgreen push ~/Downloads/my_file.php wp-content/uploads/my_file.php
# Download a file into a local folder
829 scp asphaltgreen pull wp-content/debug.log ~/Downloads/
# Upload or download a whole folder
829 scp asphaltgreen push ./my-plugin wp-content/plugins/my-plugin
829 scp asphaltgreen pull wp-content/uploads/2026 ~/Downloads/Interactive:
$ 829 scp <Tab> # fzf install picker (or: 829 scp asphaltgreen)
? I want to:
❯ Push (upload to server)
Pull (download from server)
? Source (local): ~/Downloads/my_file.php
? Destination (relative to web root): wp-content/uploads/my_file.php
Pushing /Users/you/Downloads/my_file.php → asphaltgreen:/sites/asphaltgreen/wp-content/uploads/my_file.php
my_file.php 100% 12KB 1.2MB/s 00:00
Done.The destination prompt is pre-filled with a sensible default (wp-content/uploads/<name> for push, ./<name> for pull) — press Enter to accept it.
Paths
| Side | How it's entered |
|------|------------------|
| Remote | Relative to the web root. sites/<install-id>/ is added for you, since SSH logs you in two levels above it. A pasted sites/<install-id>/… or leading / is also accepted. Paths that resolve outside the web root (e.g. ../) are rejected. |
| Local | Absolute, relative to the current directory, or ~/…. On push the source must exist; on pull the destination folder must exist. End a pull destination with / to download into that folder under the original name. |
Options
| Flag | Description |
|------|-------------|
| -y, --yes | Skip the confirmation prompt when pushing to a production install |
Notes
- Pushing to a production install always asks for confirmation unless
--yesis passed. - Transfers use
scp -O(the legacy scp protocol), which WP Engine's SSH gateway requires, and-r, so folders work without extra flags. - Existing files at the destination are overwritten without prompting.
- Requires the same SSH key setup as
829 ssh.
SSH & Portal Autocomplete
After enabling Tab completion, typing 829 ssh , 829 scp , or 829 portal and pressing Tab opens an fzf picker:
INSTALL ID DOMAIN ENVIRONMENT
absoluteenerg1 absoluteenergy.com 🌐 production
absoluteenerstg absoluteenergy.829stage.com 📝 staging
absoluteenerdev absoluteenergy.829dev.com ⚙️ developmentArrow up/down to navigate, type to filter, Enter to connect, open, or start a transfer. For 829 scp, Tab after the install ID completes push/pull and then local file paths.
Plugin Scan
829 plugin scan supports three slug modes:
| Mode | Example | Behavior |
|------|---------|----------|
| Exact | --plugin wordfence | Single report, post-scan action prompt |
| Multi-slug | --plugin wordfence,woocommerce | One report per plugin + combined comparison report |
| Wildcard | --plugin "wordpress-tools*" | Matches any installed plugin name starting with that prefix |
After an exact-slug scan you can immediately activate, deactivate, update, or delete the plugin on the matching installs.
Run
829 run executes an arbitrary shell command across any set of installs via SSH. The command is base64-encoded before sending so quotes and special characters are preserved.
829 run --cmd "wp plugin install https://github.com/org/repo/releases/download/1.8.0/plugin-1.8.0.zip --force"Output is saved to a CSV with columns: name, primary_domain, exit_code, output.
Accounts & Portal Users
Accounts
829 accounts sync caches every WP Engine account the API credentials can see to ~/.829/accounts.json. 829 accounts list browses them with a fuzzy search picker showing each account's nickname, ID, and install count (from the install cache).
Accounts are shown by their portal nickname (e.g. x829studios14) everywhere in the CLI. Older accounts also have an internal name like esm0kameh29fgb; you can search by either.
Every portal user command accepts --account <nickname|id> to skip the account picker. An exact nickname or ID match wins; otherwise it falls back to a partial match.
List users
829 portal user list opens an account picker. Choose an account to print its users in the terminal, sorted by role, then name:
x829studios14 cde81618-a6b5-4dc5-976f-d2b430c17176
NAME EMAIL ROLE
Caleb Zahnd [email protected] owner
Alena Chanto [email protected] full
…Pass --account <nickname|id> to skip the picker, and add --csv to also save a report. If a partial name matches more than one account, it lists the matches instead of guessing.
The first option in the picker, All accounts, exports every user on every account to a CSV instead. Use --all to do this without the picker:
account_name, account_id, first_name, last_name, email, role, installsinstalls is all for full-access roles, or a semicolon-separated list of install names for partial access (none if a partial user has no installs).
Add and remove users
829 portal user add # pick account, enter name/email, pick role
829 portal user delete --account x829dev # pick the user to removeBoth confirm before making any change.
Change a user's role
829 portal user promote picks an account, a user, and a new role, then confirms before applying it.
| Role | Access |
|------|--------|
| full | Every install on the account |
| full,billing | Full access plus billing |
| partial | Selected installs only — you pick them from the install cache |
| partial,billing | Partial access plus billing |
| owner | Full control of the account, including users and billing (promote only, including --all-accounts) |
Granting Owner can fail if your API credentials don't have permission on that account. When it does, the command shows the API's reason and leaves the user's role unchanged.
Set a role on every account
829 portal user promote --all-accounts sets one user's role across every account in one run:
829 portal user promote --all-accounts --email [email protected] --role fullIt checks each account first and prints a plan before changing anything:
x829studios14 already set
x829studios15 update partial → full
x829studios16 already setAfter you confirm, it applies the changes, retries if the API rate-limits, and writes a CSV report of every account to ~/829-tools/reports/.
| Flag | Description |
|------|-------------|
| --email <email> | User to update (prompted if omitted) |
| --role <role> | full, full,billing, or owner (prompted if omitted). Partial access is per-account, so use single-account promote for that. |
| --add-missing | Invite the user to accounts they aren't on yet, using their name from an account they're already on |
| -y, --yes | Skip the confirmation prompt |
Existing owners are never demoted by --all-accounts.
With --role owner, accounts where the user is already an owner show as already set. Users invited with --add-missing join as full and are then promoted, because WP Engine doesn't invite people straight in as owner. If an account refuses ownership (usually because your API credentials don't belong to one of its owners), the run carries on: an existing member keeps their role, and a newly invited one stays full. The report marks that account partial and gives WP Engine's reason.
wordpress-tools
829 wpt provision
Installs or force-updates the wordpress-tools plugin from GitHub, activates it, generates a 32-character API key, and sets it — across any number of installs in one run.
829 wpt settings
Enables or disables restrict_plugin_management across targeted installs.
829 wpt repair
Fixes installs where the plugin was installed from a GitHub ZIP archive, leaving the folder named wordpress-tools-main instead of wordpress-tools. Renames the folder and activates the plugin. If both folders exist, removes the stale one.
Cookie Scraper
Audits every cookie, localStorage entry, and sessionStorage entry set on a site's pages. Identifies the vendor behind each item (Google Analytics, HubSpot, Meta, etc.) and exports two CSV reports.
Scan via sitemap:
829 cookies https://example.com/sitemap.xmlScan a single page:
829 cookies https://example.com/aboutScan a specific list of pages via JSON file:
829 cookies --urls ./pages.jsonThe JSON file should be a plain array of URLs:
[
"https://example.com/about",
"https://example.com/contact",
"https://example.com/services"
]Options:
| Flag | Description | Default |
|------|-------------|---------|
| -u, --user <username> | Basic auth username | — |
| -p, --pass <password> | Basic auth password | — |
| -c, --concurrency <n> | Pages to scrape in parallel | 3 |
| -o, --output <dir> | Output directory for CSV files | ~/829-tools/reports/ |
| --max-pages <n> | Cap number of pages (useful for testing) | — |
| --urls <file> | JSON file containing an array of URLs to scan | — |
| --by-page | Also generate the per-page detail report | — |
| --debug | Print per-page cookie capture diagnostics | — |
Output files (written to ~/829-tools/reports/ by default):
cookie-summary-<timestamp>.csv— one row per unique cookie/storage key, with vendor, domain, attributes, page count, and sample valuescookie-by-page-<timestamp>.csv— generated only when--by-pageis passed; one row per item per page
Site Crawler
Crawls a site and exports a CSV inventory of every page with SEO-relevant data (status, title, meta, H1s, word count, links, etc.).
Crawl via sitemap:
829 crawl https://example.com/sitemap.xmlCrawl by following links from a start URL:
829 crawl https://example.com --max-depth 3 --max-pages 200Render JS before parsing (for SPAs / client-rendered sites):
829 crawl https://app.example.com --renderOptions:
| Flag | Description | Default |
|------|-------------|---------|
| -u, --user <username> | Basic auth username | — |
| -p, --pass <password> | Basic auth password | — |
| -c, --concurrency <n> | Pages to fetch in parallel | 5 (3 with --render) |
| -o, --output <dir> | Output directory for CSV files | ~/829-tools/reports/ |
| --max-pages <n> | Cap the number of pages crawled | — |
| --max-depth <n> | Max link depth from start URL (crawl mode only) | 5 |
| --urls <file> | JSON file containing an array of URLs | — |
| --render | Use Puppeteer to render JS before parsing | — |
| --ignore-robots | Ignore robots.txt disallow rules | — |
| --debug | Print per-page diagnostics | — |
Output: crawl-<timestamp>.csv — one row per page with: url, status_code, title, meta_description, h1, canonical, word_count, internal_links_count, external_links_count, images_missing_alt, and more.
Output Files
Reports and logs are written to ~/829-tools/:
~/829-tools/reports/ CSV reports from scans, actions, provisioning, user lists and role changes, cookie audits, and crawls
~/829-tools/logs/ Detailed logs of SSH session outputCached data lives in ~/.829/:
~/.829/installs.json Install list from `829 installs sync`
~/.829/accounts.json Account list from `829 accounts sync`Updating
npm update -g 829cli
829 installs sync
829 accounts sync