Remote workers & wp-executor

The remote.execute_command node offloads work to a wp-executor binary running on a host you operate. The WordPress plugin never executes the command itself — it enqueues a job and the external worker picks it up.

Architecture

WordPress (plugin)                Your host
     │                               │
     ├─ POST /remote/queue ─────────→│  (enqueue job)
     │                               │
     │  ←── GET /remote/queue/claim ─┤  (worker claims job)
     │                               │
     │  ←── POST heartbeat ──────────┤  (lease extension)
     │                               │
     │  ←── POST result ─────────────┤  (job completed)
     │                               │
     └─ command_completed trigger ───┘  (resume workflow)

Setting up wp-executor

1. Download the wp-executor binary for your OS/architecture
2. Create a config.toml with your WordPress URL and bearer token
3. Run wp-executor --config config.toml

Creating a worker in the admin

1. Go to PF Workflow → click the executor badge (bottom-right floating button)
2. Click "Create Worker"
3. Give it a name and select which capabilities to grant: - shell.run — run system commands - fs.read / fs.write / fs.list — filesystem access - http.request — make outbound HTTP requests - system.info — read system information
4. Copy the bearer token (shown only once after creation)
5. Paste it into your wp-executor config.toml

Worker management

Security

• Workers authenticate via bearer token
• Optional HMAC request signing (sign_requests = true in config.toml)
• Per-worker capability whitelist
• Lease-based job claiming (60s default)
• Heartbeat-based lease extension