Commands

The Commands tab lets you run shell commands inside your project's active release directory — the same place your application runs. Useful for cache clears, database tinkering, Laravel artisan commands, and other ad-hoc maintenance work without dropping into SSH.

Open it from the project's tab strip in the Console.

Running a command

Type the command into the input at the top and click Run (or hit Enter). The command runs as the depfloy user from the project's current/ directory.

php artisan cache:clear
php artisan migrate --force
npm run db:seed

While the command runs, its standard output and error streams in live below the input. The command's exit code shows up at the end so you can tell whether it succeeded.

You can keep typing into the input while a previous command is still streaming — your second command queues and runs after the first finishes.

Command history

The list below the input shows your recent commands with their full output. Click any entry to expand and re-read the output. Click Re-run on an entry to run it again without retyping.

What you can and can't run

The Commands tab is for one-shot commands — things that start, do their work, and exit. Examples that work well:

• php artisan migrate
• npm run build (though you usually want this in your build pipeline, not here)
• composer dump-autoload
• tail -n 200 storage/logs/laravel.log

What doesn't work well:

• Long-running daemons — they'll block the Commands tab indefinitely. Use Background Jobs for processes that should stay alive.
• Interactive prompts — commands that wait for input (without -y / --force) will hang. Make sure the commands you run here are non-interactive.

Who can run commands

Commands can change application state and access secrets, so they require the same permission as updating the project — Owner, Admin, Manager, or Developer. See Members.