Run development and deployment tools with the PHP and Node packages selected in PXM. Project commands execute application code as your Unix account, so use projects and dependencies you trust.
Composer
pxm composer --version pxm composer install
PXM downloads Composer from its official distribution and verifies its published SHA-256 before running it with managed PHP. Cached copies have a verified receipt. Application dependency resolution follows the project's Composer files and configured repositories.
Project workers
pxm task list app.example.com pxm task start app.example.com queue pxm task start app.example.com scheduler pxm task start app.example.com reverb --port 8080 pxm task start app.example.com frontend --port 5173 pxm task logs app.example.com queue pxm task restart app.example.com queue pxm task stop app.example.com queue
Tasks are attached to a registered site and use its managed runtime and project directory. Available kinds are queue, scheduler, reverb, frontend, composer-install and npm-install. Persistent tasks can use --autostart on or --autostart off. Dependency installation tasks are one-shot commands. Frontend and Reverb listeners use the explicit private port you select; public routing remains a separate website setting.
pxm tinker app.example.com
Tinker runs the registered Laravel application's own Artisan command with its managed PHP runtime. It is interactive and can modify application data. Project task control and Tinker require PXM Pro.
Connect a coding agent
pxm mcp config
Copy the returned configuration into an MCP-compatible client on the same Linux account. The server uses standard input and output rather than a network listener. On a remote machine, run it through your client's secure SSH setup under the account that owns PXM.
pxm mcp serve
The default tool set is read-only. It reports sites, runtimes, services, health, backup plans, tasks, sharing and opt-in diagnostics without exposing stored database passwords or license keys. Project text and logs remain untrusted application content. MCP access requires PXM Pro.
To permit management tools, deliberately generate a configuration with writes enabled:
pxm mcp config --allow-writes
Write tools can start sites and services, manage project tasks and request backups or compatible updates. Interrupting or publishing operations require an explicit confirmation argument. The server accepts only its declared tools and validated parameters; it does not offer arbitrary shell execution. Authorize each operation in your coding client before allowing it to run.
See diagnostics for Xdebug, coverage and application capture, and site templates for new applications.