Filament Command Runner Laravel Package

Product Decisions This Supports

• Build vs. Buy: Eliminates the need to build a custom solution for background command execution in Filament, saving development time and reducing technical debt.
• Feature Expansion: Enables non-technical stakeholders (e.g., content managers, admins) to trigger long-running tasks (e.g., cron jobs, data imports, backups) without CLI access.
• Roadmap Prioritization: Accelerates delivery of self-service operations in admin panels, reducing reliance on engineering for routine maintenance tasks.
• Use Cases:
  • Automated workflows: Trigger Laravel jobs (e.g., queue:work, schedule:run) via UI.
  • Data operations: Run migrate, db:seed, or custom scripts without SSH.
  • Monitoring: Track command execution history and logs in real-time.
  • Multi-tenant SaaS: Allow tenants to manage their own background tasks (e.g., storage:link for their assets).

When to Consider This Package

Adopt if:

• Your team uses Filament for admin panels and needs to expose CLI commands to non-developers.
• Commands are long-running (e.g., >30 seconds) and block the UI if run synchronously.
• You lack a dedicated task queue system (e.g., Laravel Horizon) or need a lightweight alternative.
• Your stakeholders require audit trails for command execution (logs, timestamps, statuses).

Look elsewhere if:

• You need real-time progress updates (e.g., percentage completion) beyond basic output streaming.
• Commands require interactive input (e.g., make:model prompts).
• Your team prefers serverless/queue-based solutions (e.g., Laravel Forge + Queues) over UI-triggered execution.
• Security policies prohibit shell command execution in the admin panel (requires careful permission gating).

How to Pitch It (Stakeholders)

For Executives: "This plugin lets non-technical teams run critical backend tasks (like database updates or backups) directly from the admin dashboard—without waiting or needing CLI access. It’s like giving your content managers a ‘Run’ button for server tasks, reducing engineering bottlenecks and speeding up operations. Low-risk (MIT license), lightweight, and integrates seamlessly with Filament."

For Engineering: *"A drop-in solution to expose Artisan/shell commands via Filament with background execution and log tracking. Saves ~2–4 weeks of dev time vs. building a custom queue UI. Key benefits:

• No UI blocking: Commands run async; users get a job ID to check later.
• Security: Role-based command whitelisting (e.g., only admins can run migrate).
• Observability: Logs and statuses stored in the DB for debugging.
• Future-proof: Extensible for custom command handlers or integrations (e.g., Slack alerts on failure). Tradeoff: Limited to Filament; requires PHP/Laravel stack. Recommend piloting with low-risk commands (e.g., cache:clear)."*