Once the server is configured, you ask questions in plain language and your assistant picks the tool. No commands, no syntax. The sections below show the questions each tool is good at.
Finding compatible versions
Which versions of a package work with a dependency you already have pinned:
What versions of Livewire are compatible with Laravel 11?
Can I use Inertia with illuminate/support ^10.0?
Which major versions of @inertiajs/react work with React 18?
Show me Vue versions that support TypeScript 5
This is the one to lean on when planning a framework upgrade or untangling a dependency conflict.
Getting release notes
What changed between two versions, pulled from GitHub releases:
What changed in Laravel from 11.0 to 11.1?
Show me release notes for Symfony Console between 6.0 and 6.4
What are the breaking changes in React from 17 to 18?
Summarize updates in tailwindcss from 3.0.0 to 4.0.0
Useful for sizing up an upgrade before you start it, and for writing the notes afterwards.
Checking available upgrades
The latest patch, minor, and major release you could move to:
What's the latest version of symfony/console I can upgrade to?
Show me upgrade options for Laravel from 10.0.0
What are the available upgrades for lodash from 4.17.0?
Is there a new major version of Vue available?
Asking for all three at once tells you whether an update is a patch you can take today or a major you need to schedule.
Inspecting dependencies
Everything a specific version of a package requires:
What does Laravel 12 require as dependencies?
Show me what React 18.2.0 depends on
What are the requirements for Symfony 7.0?
Does Livewire 3 require Alpine.js?
For npm packages this includes peer dependencies, which is usually where upgrade conflicts hide.
For parameters and return shapes, see the tool reference. For analysing your own project rather than the registries, see the CLI.