Laravel, WordPress, Node.js, and worker tools.
Framework tools provide safe, task-specific operations on top of the common deployment, process, file, and log model.
Laravel applications can use guided installation, generated application keys, standard deployment hooks, queue workers, the scheduler, and Octane with Swoole.
Artisan commands run from a vetted catalog. A team may extend the allowlist with trusted command paths. Arguments are tokenized into an argv array and executed directly as the application user.
php artisan migrate --force
php artisan queue:restart
php artisan storage:linkQueue workers expose queue name, process count, timeout, sleep interval, retry count, state, and stdout or stderr. Octane exposes readiness and a safe runtime reload.
ServerChirp can install standard WordPress or Composer-managed Bedrock with generated salts and database settings. WordPress applications receive appropriate Nginx defaults and optional hardening snippets.
WP-CLI uses the same vetted argv execution path as Artisan. Database search-and-replace supports a preview before applying changes and reports what changed.
Node.js and Bun applications can use detected package managers, build and runtime commands, health checks, resource limits, and the managed application runner.
Supervisor-managed BullMQ workers define script, queue, concurrency, process count, Redis URL, and memory. Registered queues show waiting, active, delayed, failed, and completed counts. Authorized operators can retry failed jobs or remove jobs from a selected state.
User-authored commands never pass through a shell behind a metacharacter denylist. ServerChirp tokenizes them and the agent executes the argv array under the application user's UID and GID with an explicit environment and owner-checked release directory.