- How do I install pragmarx/artisan-tool in a Laravel app?
- Install it with Composer using composer require pragmarx/artisan-tool and rely on Laravel package auto-discovery to register the service provider. No configuration is required for the basic setup, which matches the package's zero-configuration positioning. If you are using the Nova-based interpretation, you will also need to publish assets and register the tool in NovaServiceProvider::tools(). Verify the actual integration steps against the repository before committing, because the package's own metadata is ambiguous.
- Is pragmarx/artisan-tool a Nova tool or a programmatic Artisan wrapper?
- The repository description and the package documentation disagree: one describes bringing Artisan to Nova, the other describes a code-level wrapper around Artisan::call() with output capture. These are very different products with very different risk profiles. Confirm which one you are installing before approving a spike or writing integration code, because the answer determines whether you need Nova at all.
- Does pragmarx/artisan-tool work without Laravel Nova?
- If the package is genuinely a Nova tool, it requires an existing Nova installation and there is no partial fit without it. If it is only a programmatic wrapper around Artisan::call(), Nova is irrelevant. Because the metadata is ambiguous, verify this first; adopting Nova solely to run Artisan commands is far out of proportion to the benefit.
- What Laravel versions does pragmarx/artisan-tool support?
- The available context does not state explicit laravel/framework constraints, so check the composer.json require block and the repository release history. Nova 4 and 5 changed tool registration and asset conventions in ways that can silently break older tools, so validate against your exact Nova major. Do not assume compatibility from the package name or description alone.
- How is pragmarx/artisan-tool different from Laravel's make:command?
- The overview says it complements rather than replaces make:command, adding helper commands for scaffolding signatures and inspecting registered commands. Think of it as a convenience layer over the standard generator, not a substitute. If you only need to create a command occasionally, the built-in generator is sufficient and carries no third-party dependency risk.
- Is it safe to run Artisan commands from the browser in production?
- Only with guardrails. A browser-accessible command execution surface sits in an application's most privileged administrative plane, so you need a Gate policy, a curated command allowlist, audit logging, environment gating, timeout handling, and exit-code validation. Commands execute as the web server user, which means database grants, filesystem permissions, and git behavior can differ from what an operator expects from an SSH session. Interactive prompts have no stdin and may hang or fail silently.
- Does pragmarx/artisan-tool capture stdout, stderr, and non-zero exit codes?
- The documentation describes output capture around Artisan::call(), but you should verify with a deliberately failing command rather than trusting a documented claim. Confirm that stderr and non-zero exit codes are surfaced in the UI, because a failing command that renders as successful is an observability gap that looks like a package bug. Also determine whether execution is in-process or a subprocess, since that drives timeout behavior, environment isolation, and output fidelity.
- Can I restrict which Artisan commands are exposed?
- Whether the package ships a real allowlist or only cosmetic configuration settings is one of the key questions to answer in an evaluation spike. If free-form command input is accepted, you must add your own allowlist before exposing the tool to anyone. Treat a published config file as unverified until you have tested that disallowed commands are actually blocked.
- How do I roll back or disable pragmarx/artisan-tool?
- The rollback is removing the tool registration line from NovaServiceProvider::tools() or uninstalling the Composer package, depending on which interpretation is correct. Define this one-config-change rollback before deployment and confirm that a non-admin account sees the tool as absent rather than merely disabled. A clean rollback path matters more for a low-adoption dependency than for a well-maintained one.
- Is pragmarx/artisan-tool actively maintained, and what are the alternatives?
- The package sits at roughly 34 stars with zero dependents and sparse documentation, so there is little community pressure on fixes and you should expect to own most issues yourself. Alternatives include Laravel's built-in make:command for scaffolding, a custom Nova tool for a curated admin console, or a deploy script and CI job if you only need to run commands remotely. For teams without Nova, a deploy script or CI job is the correct answer.