Congrats, Ashley! Can't wait to play around with this.

@ashleyhindle On a brand new project w/Boost, Claude's first instinct was to execute "artisan make:controller" from within Tinker rather than CLI. Worth adding guidance about that?

Thanks for the hard work Ashley! As the first French Laravel "tutorials" representative, I'd like you to know I recorded something about this splendiferous package! piped.video/wxHY6MWAh1U

This is awesome to see, great work! 🙏 The cursor agent that was just released works better with MCP now, so you might see an improvement there after upgrading too 👌 I always test my MCP connection with "what models does application-info say I have?" when I set Boost up in a project 💪

Awesome! Quick Q - Any plans to add Laravel Telescope support? @marcelpociot seems to have this sort of debug loop assistance wrapped up from a Herd point of view

Is there a recommended way to use in a monorepo? I had to move the .vscode/mcp.json to the root of the project, not sure if I need to pay attention to other things.

How do you mean? Does your repo have multiple projects within it? There aren't recommended ways for many things at the minute, but happy to give a steer 👌

Will you post somewhere about your testing/benchmarks? Was listening to the podcast and would find it really interesting

Oh absolutely - I was too optimistic with it and was hoping it would be ready today 😆 But some time within the next month? I hope to be finished 🤞

Nice nice! Thanks for the good work, Ashley. Curiosity, you mentioned @filamentphp on stage when announcing Boost, but it's conspicuously absent. In the works?

It shouldn't be conspicuously absent, @pushpak1300 and I worked hard on ingesting Filament docs & creating Filament AI guidelines from scratch, with the help of @danjharrin Is it not working for you?

This is exciting. Never tried an MCP what Agent/models do people recommend paying for as a solo developer?

Amazing work, @ashleyhindle ! Congrats on the release

Loving this package, thanks Ashley & team! 🚀 Keyword-matched tests are super handy, but it’d be awesome if it then re-ran the full test class once the change passed.

This was in the original guidelines, but internally for larger projects where test suites take a long time it got in the way more than it helped. You could add a `.ai/guidelines/full-suite.php` file, add "You must always run the full test suit after finalizing changes", then boost:install to have it added to your guidelines 👌

Question: what if my app runs in container?

That can work by running something like `docker exec` to `php artisan boost:mcp` or running it on your host if you have PHP on the host Just a couple more steps at the minute !

are there plans to support gemini cli?

You can add Boost to gemini cli now if you update your .gemini/settings.json file 🙌