Import Export by RockStarLab 2.1.59 makes the WP-CLI job commands work with Content Sync, so a deployment script can push content from staging to production and check the result.
Free: the fix is in the free plugin. PRO: no change; PRO 2.1.16 works with 2.1.59.
job get and job wait read Content Sync jobs
A push, pull or media sync started from WP-CLI with an ability, for example wp rsl-ie ability sync-push-start, creates a Content Sync job. From 2.1.59, wp rsl-ie job get and wp rsl-ie job wait accept that job. job wait runs it in the WP-CLI process until it finishes, then prints the totals:

The exit code is 0 when the job is done and 1 when it fails. When a media file is missing on the other site, the failed file is listed as a warning. Before 2.1.59, both commands stopped with “job_runner_unavailable” for Content Sync jobs.
How to update
Update from Dashboard → Updates on all connected sites. Connections, jobs and schedules stay as they are. As before any update, back up the site first.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) reads the same jobs without WP-CLI:
What did the last content push send to production?
In our run, the agent called rsl-ie/job-list and rsl-ie/sync-job-status: 2 posts updated and 1 image synced.
FAQ
Do I need WP-Cron for a push from WP-CLI?
No. wp rsl-ie job wait runs the job in the WP-CLI process.
Do import and export jobs change?
No. job get and job wait work for them as before.
Do I need to update PRO?
No. PRO stays at 2.1.16.
Related Guides
- File Hash Column in the Media Export (What’s New in 2.1.60)
- Media Library Sync in Batches (What’s New in 2.1.58)
- WP-CLI Import and Export for WordPress: CSV, Excel and Cron Scripts
Get the free plugin on WordPress.org.

Comments 0
Have a question or a tip to share? Leave it below.