Jonathan Lahijani Posted May 28 Posted May 28 CliModules The "native" way to do CLI with ProcessWire as of April 2026 Forum post Developer: @ryan processwire-console Based on Symfony CLI. Installed via composer local to project / in composer.json. Very deep functionality and the most developed; also includes Scheduling, Testing, Queues, Migrations, Seeding; released May 2026 Forum Post ; GitHub Developer: @ukyo RockShell Based on Symfony CLI. Installed via placing RockShell dir in root of PW; released 2022 Forum Post ; GitHub Developer: @bernhard WireCLI Based on Symfony CLI. Installed via composer globally; released 2023 Forum Post ; GitHub Developer: @flydev Wire-Shell Based on Symfony CLI. This project died a while ago. --- I suppose the reason I'm posting this is to start a discussion. Should there ultimately be "one true way"? If CliModules approach "wins", does the fact that it's dependency free (ie, not based on Symfony CLI, as ProcessWire is more of a unified system) pose any potential limitations? Note: I'm personally going to be using some combination of CliModules and processwire-console moving forward. 5
ryan Posted May 28 Posted May 28 I agree with Zilli, and don't think there needs to be "one true way". I would use whatever helps you get your work done. ProcessWire's CLI is a fairly recent addition, but it's one that's going to keep expanding. There's also no chance of it getting abandoned. I think we should aim to continue having multiple CLI projects moving forward, both core and 3rd party. While there will be some overlap, it's also clear that all the projects have their own benefits, so it may even be worth using more than one together. 5
Recommended Posts