rtk-ai/rtk

Add PHP and laravel (artisan, sale) commands

Open

#2,245 opened on Jun 3, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Description

Context

Running rtk discover on my project revealed that 284 out of 675 unhandled commands are Laravel Sail variants — making it the single largest savings opportunity not yet covered by RTK.

Top unhandled commands

Command Count Example
sail artisan 148 vendor/bin/sail artisan test --testsuite=...
sail exec 82 vendor/bin/sail exec pgsql psql -U sail...
sail bin 54 vendor/bin/sail bin pint --dirty --format=...
sail composer 4 vendor/bin/sail composer require ...

What I'd expect

RTK wrappers similar to existing ones, e.g.:


rtk sail artisan <args>   →  vendor/bin/sail artisan <args>

rtk sail exec <args>      →  vendor/bin/sail exec <args>

rtk sail bin <args>       →  vendor/bin/sail bin <args>

rtk sail composer <args>  →  vendor/bin/sail composer <args>

Or alternatively — a generic rtk sail <subcommand> <args> that proxies all Sail subcommands.

Why it matters

Laravel Sail is the standard Docker-based dev environment for Laravel projects. These commands produce large tool_result outputs (test runners, psql sessions, code formatters), so RTK's token-saving behavior would be particularly valuable here.

Contributor guide