#Clawdbot Installation on Windows CMD

1 messages · Page 1 of 1 (latest)

stable estuary
#

Clawdbot installed successfully on windows but when it says starting set up, this error pops up

clawdbot : The term 'clawdbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\AGYENIM\AppData\Local\Temp\clawdbot-install.ps1:429 char:13

  •         clawdbot onboard
    
  •         ~~~~
    
    • CategoryInfo : ObjectNotFound: (clawdbot:String) [], ParentContainsErrorRecordException
    • FullyQualifiedErrorId : CommandNotFoundException
iron hareBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

patent hatchBOT
# stable estuary Clawdbot installed successfully on windows but when it says starting set up, thi...

This is a classic Windows PATH issue. The Clawdbot CLI was installed, but the terminal session doesn't have the updated PATH.

Quick fix:

  1. Close the current terminal completely and open a new one (CMD or PowerShell), then try clawdbot onboard again

  2. If that doesn't work, the npm global bin directory needs to be in PATH manually:

    npm config get prefix
    

    The output (usually C:\Users\YOUR_USERNAME\AppData\Roaming\npm) should be in your PATH.

  3. To verify PATH in PowerShell:

    $env:PATH -split ";" | Select-String "npm"
    
#
  1. If missing, add it:

    [Environment]::SetEnvironmentVariable("PATH", $env:PATH + ";C:\Users\YOUR_USERNAME\AppData\Roaming\npm", "User")
    

    Then restart your terminal.

  2. Alternatively, just run the full path directly:

    C:\Users\AGYENIM\AppData\Roaming\npm\clawdbot onboard
    

The key issue is the terminal needs the updated PATH environment after installation. Most users fix this by simply closing and reopening their terminal. 🦐

stable estuary
#

still getting the same error

patent hatchBOT
# stable estuary still getting the same error

Let's verify if Clawdbot was actually installed:

Check if the command exists:

where clawdbot

If nothing shows, the install didn't work. Try reinstalling with verbose output:

Reinstall with npm directly:

npm uninstall -g clawdbot
npm install -g clawdbot

Then check the install location:

#
npm list -g clawdbot --depth=0

Also check if npm global bin is in your PATH:

npm bin -g

This should return the path. If it fails, npm's global bin isn't set up correctly on your system.


Can you share:

  1. Output of where clawdbot
  2. Output of npm bin -g
#

That will tell us if it's a PATH issue or if the install never completed. 🦐

stable estuary
#

when i try the install…this is what I’m getting

#

[OK] Windows detected
[OK] Node.js v24.13.0 found
[*] Installing Clawdbot@latest...
npm error code ENOENT
npm error syscall spawn git
npm error path git
npm error errno -4058
npm error enoent An unknown git error occurred
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: C:\Users\AGYENIM\AppData\Local\npm-cache_logs\2026-01-25T04_40_13_772Z-debug-0.log
[OK] Clawdbot installed

Clawdbot installed successfully!

Ahh nice, I like it here. Got any snacks?

Starting setup...

clawdbot : The term 'clawdbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\AGYENIM\AppData\Local\Temp\clawdbot-install.ps1:429 char:13

  •         clawdbot onboard
    
  •         ~~~~
    
    • CategoryInfo : ObjectNotFound: (clawdbot:String) [], ParentContainsErrorRecordException
    • FullyQualifiedErrorId : CommandNotFoundException
patent hatchBOT
patent hatchBOT
#
  1. Then retry the Clawdbot install:
    npm uninstall -g clawdbot 2>$null
    npm install -g clawdbot
    

The "Clawdbot installed successfully!" message was misleading - npm actually failed during the install, so the CLI was never properly installed. Once git is in PATH, npm will work correctly. 🦐

stable estuary
#

i got this error when I tried the fix

[OK] Windows detected
[OK] Node.js v24.13.0 found
[*] Installing Clawdbot@latest...
npm error code ENOENT
npm error syscall spawn git
npm error path git
npm error errno -4058
npm error enoent An unknown git error occurred
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: C:\Users\AGYENIM\AppData\Local\npm-cache_logs\2026-01-25T04_40_13_772Z-debug-0.log

patent hatchBOT
# stable estuary i got this error when I tried the fix [OK] Windows detected [OK] Node.js v24.1...

Did you restart your terminal after installing Git? The PATH won't update until you close and reopen PowerShell/CMD.

First, verify Git is now in your system:

where git

This should return something like C:\Program Files\Git\cmd\git.exe

If it returns nothing: Git wasn't installed with PATH option, or you need to restart terminal.

If it returns a path: Then try installing again:

npm uninstall -g clawdbot 2>$null
#
npm install -g clawdbot

Let me know what where git shows! 🦐

stable estuary
#

where git shows

INFO: Could not find files for the given pattern(s)

#

and I have restarted CMD but it’s still not returning anything

patent hatchBOT
# stable estuary where git shows INFO: Could not find files for the given pattern(s)

Git isn't in your PATH yet. Let's check if it's installed at all:

Check if Git exists on your system:

dir "C:\Program Files\Git\cmd\git.exe"

Or just try:

git --version

If neither works:

  1. You may need to re-run the Git installer and make sure you:
    • ✅ Check "Add Git to PATH" during installation
    • ✅ Use the "Git from the command line and also from 3rd-party software" option
#
  1. After installer completes, close PowerShell completely and open a new one

  2. Verify:

    git --version
    

You should see something like git version 2.x.x

Once git --version works, then npm install -g clawdbot will work too. 🦐

patent hatchBOT
# stable estuary and I have restarted CMD but it’s still not returning anything

Git isn't installed on your machine. The installer either didn't run or was cancelled.

Download and run the Git installer:

  1. Download: https://git-scm.com/download/win

  2. During installation, VERY IMPORTANT:

    • ✅ Select "Add Git to PATH" (this is critical!)
    • ✅ Choose "Git from the command line and also from 3rd-party software"
    • ✅ Everything else can stay as default
  3. Complete the installation (don't cancel)

  4. Close CMD completely (the window) and open a new one

  5. Test:

#
   git --version

You should see git version x.x.x after that.

Once git works, then:

npm uninstall -g clawdbot 2>$null
npm install -g clawdbot

Let me know once you've run the installer! 🦐

stable estuary
#

my CMD is stuck here

Install gateway service now?|
Yes|
*
Gateway service runtime|

Node (recommended) (Required for WhatsApp + Telegram. Bun can corrupt memory on reconnect.)

patent hatchBOT
# stable estuary my CMD is stuck here Install gateway service now?| Yes| * Gateway service...

Great progress! The installation is working now. 🎉

Press Enter to select "Yes" (it's already highlighted with the asterisk *)

Then for the next prompt, press Enter again to select "Node" (it's the recommended option).

The setup should continue automatically from there!

If you need to navigate:

  • Enter = confirm selection
  • Arrow keys = move between options

Let me know what happens after you press Enter! 🦐

stable estuary
#

it says doctor complete

patent hatchBOT
# stable estuary it says doctor complete

Excellent! 🎉

Clawdbot is now installed! The "doctor" check passed, meaning your system is ready.

Next step - run the setup:

clawdbot onboard

This will:

  1. Create your config file
  2. Guide you through connecting channels (WhatsApp, Telegram, etc.)
  3. Set up your AI model preferences

Note: If you see a QR code, scan it with WhatsApp to link your account.