Skip to content

Commands

TheFactoryGuy edited this page Nov 2, 2026 · 2 revisions

Sometimes a command has to run in your project, such as npm run db:migrate or npm install. You never need to type it into a terminal: Coodoo does it for you.

Where you see them

A command shows up as a card with a short explanation and the Let Coodoo do this button:

  • in the Chat, when the agent suggests running something;
  • at the top of the Goals window, under Coodoo needs you, when the team left something ready for you after a goal (for example after you fill in a key);
  • in the App panel, when your app needs something once before its first start.

Running it

  1. Read what the command does. With npm run … you also see what that script runs.
  2. Click Let Coodoo do this. You see the output live; Stop cancels it.
  3. Done or Failed appears at the top of the card. If it failed, click Ask what went wrong: the chat gets the error and explains what you can do.

Coodoo uses the Node, Python or Java it installed for this project (see Requirements), and the keys from Your app's settings.

What Coodoo won't run

Coodoo checks every command first. It only runs developer tools (such as npm, npx, pnpm, yarn, pip, python or cargo) and refuses:

  • several commands chained together, or characters like |, ;, > and $;
  • sudo, installing something globally (-g) and anything outside your project;
  • publishing or logging in (npm publish, npm login);
  • tools that aren't in your project yet (npx doesn't fetch anything loose from the internet);
  • code written straight on the command line (node -e, python -c).

If a command is refused, you see why. Nothing runs unless you click, and not while the autopilot is working.

Clone this wiki locally