A wall of red text after an install command is discouraging, but most failures come from the same few causes, and you can rule them out one by one.
- 1Read the last lines of the errorand match them in the table
- 2Use the official steps for your system
- 3Check what it needsaccount, key, Node.js, OS version
- 4Start again cleanly
- 5Ask for helpgoal, system, command, full error, screenshot
Fixed at any step? Stop there.
Read the end of the error
The useful part of an error is nearly always at the bottom, often on the first line that starts with Error. Copy the whole message into a note before you do anything else; you will need it if you ask for help. Then look for one of these:
| You see | It usually means | Try |
|---|---|---|
command not found, is not recognized | The program is not installed, or this terminal cannot find it yet | Open a new terminal window; check that the install step finished |
permission denied, EACCES, Access is denied | The installer tried to write somewhere it is not allowed | Use the install method the official guide gives for your system, rather than adding sudo or running as administrator |
node: not found, requires Node.js 20 | A program it depends on is missing or too old | Install or update it from its official site, then try again |
401, unauthorized, invalid API key | The key or sign-in is wrong or has expired | Sign in again, or create a new key in the provider's dashboard |
429, rate limit, quota | You hit your plan's or key's limit | Wait, check your billing, or try a smaller task |
ENOTFOUND, ECONNRESET, timed out | The network blocked the connection | Try another network; company networks and VPNs often block these tools |
Check you used the steps for your system
Install guides go out of date quickly, and a command copied from a three-month-old blog post may no longer work. The steps on each project's page in the Library come from the creator's own instructions. Make sure you used the one for your system, because Mac, Windows and Linux often differ.
On Windows, some projects only run inside WSL, a Linux environment you install on top of Windows. The project's page lists the systems it supports.
Check what it needs
Most "it just won't start" problems are something missing from "Before you start" on the project's page. Usually it is an account or paid plan with the AI company, an API key without billing set up, another program such as Node.js, Python or Docker, or an operating system that is too old.
Start again cleanly
After a few attempts you can end up with half-installed versions fighting each other. Remove what you installed using the project's own uninstall steps, close every terminal window, and install once more following only the official guide.
Ask for help
Whether you ask the project's community or us, a complete request gets a fast answer. Say what you were trying to do in one sentence, which system and version you are on, the exact command you ran, and the full error as text rather than a photo of the screen. Add a screenshot if the problem shows up in a window or a web page, and mention what you already tried.
Leave out passwords, API keys and tokens. If a key appears in the error text, replace it with xxxx before sending.
A bug in the project itself belongs in the creator's repository; the link is on every project page. If you would rather have someone look at your setup with you, Get help asks for exactly the details above, and we reply with a plan and a price before any paid work starts.