Start with the step that failed
Decide whether the tool did not start, a request was refused, the installer failed, the command itself failed or the check afterwards failed. Each shows a different sign, and fixing the wrong one wastes a retry.
The tool disconnects before it starts
Check that the tool is installed where your agent runs and that your agent’s configuration points to it. Try starting it by hand in the same place. A tool that looks stuck in a terminal is only waiting for your agent.
The tools do not appear, or have a different name
Through the tool registry the tools carry the backend’s name in front, and a session may list only the ones you enabled. The MAIT image has the tool installed but not registered: add it to the registry if it is missing, enable its tools for the session and use the names your agent lists.
The tool cannot run the installer
The installer or the project folder cannot be used. Give the full location of both and restart the tool. Do not add extra words to the location of the installer.
A request is refused, or the answer has no clear result
A request without an action, a tool name or a version is refused before anything runs. Ask your agent to read the current list of tools and use their published names, then read the error flag and the text of the answer: it says what ran, how it ended and whether the output was cut.
Setup finishes but tools are missing
Use the full path of the project folder that holds its tool list. One tool can fail to install while setup still ends well, so read the message for each tool and list what is installed afterwards. A failed command does not undo what it already did.
The activation does not reach the session you expect
Ask for the current selection in the same project and check its scope. A session selection follows the shell the tool started from, not your conversation. Choose a project selection for a lasting choice.
An upgrade only shows a preview, or an uninstall only reminds you
Upgrades show a preview first: review it, then repeat the same request and ask for the change to be applied. An uninstall without confirmation only returns a reminder. Upgrading everything can succeed while one tool fails, so compare fresh lists with what you intended.
The output is cut off, or the call runs out of time
Cut-off output means it was too long; ask about one tool at a time. Commands wait up to 15 minutes, and running out of time does not undo anything. Look at the state before you try again.
What you getThe step that failed named, and a retry aimed at the right project.