Skip to content

Troubleshooting

[katachi] ⚠ Failed to download cloudflared after 3 attempts

Fix: Retry the download:

Terminal window
npm rebuild @katachi/agent

If that doesn’t work, install cloudflared manually and set CLOUDFLARED_SKIP=1:

Terminal window
# macOS
brew install cloudflared
# Windows
winget install Cloudflare.cloudflared
# Linux (Debian/Ubuntu)
curl -L https://pkg.cloudflare.com/cloudflare-main.gpg | sudo tee /usr/share/keyrings/cloudflare-archive-keyring.gpg
echo 'deb [signed-by=/usr/share/keyrings/cloudflare-archive-keyring.gpg] https://pkg.cloudflare.com/cloudflared any main' | sudo tee /etc/apt/sources.list.d/cloudflared.list
sudo apt update && sudo apt install cloudflared

Windows (PowerShell): Close and reopen your terminal after npm install -g. npm’s global bin directory may not be in your PATH for the current session.

Linux/macOS: Ensure npm’s global bin directory is in your PATH:

Terminal window
export PATH="$(npm config get prefix)/bin:$PATH"
✗ Katachi agent failed to start

Common causes:

  1. Port conflict — Another process is using port 7676:

    Terminal window
    katachi start --port 3001
  2. Stale process — A previous agent didn’t clean up:

    Terminal window
    katachi stop
    katachi start
  3. Missing credentials — If credentials are corrupted:

    Terminal window
    katachi unregister --force
    katachi start

Check agent status:

Terminal window
katachi status

Common causes:

  1. Agent not running — Start it with katachi start
  2. Network issue — Ensure outbound HTTPS (port 443) is allowed
  3. Tunnel reconnecting — Wait 30 seconds; cloudflared auto-reconnects

The agent loads AI SDKs on demand. If memory usage is excessive:

Terminal window
katachi restart

Fix: Make sure you’re visiting the correct URL and entering the code within 15 minutes. If it expires, stop and restart the agent:

Terminal window
katachi stop
katachi start

Common causes:

  1. Session expired — Log out and log back in at katachi.live
  2. Subscription inactive — Check your subscription status in Settings
  1. Check logs: katachi logs -f
  2. Enable debug mode: katachi start --debug
  3. Contact support: [email protected]

If the agent loses access to your repository or fails to pull/push:

  1. Check local git credentials — Make sure you can pull from the terminal manually.
  2. SSH keys — If using SSH, ensure ssh-agent is running or keys don’t require passwords.

When your local agent’s branch and the remote branch diverge (e.g., after a force push or editing on multiple machines):

  1. Manual intervention — Open your terminal and resolve it manually:
    Terminal window
    git pull --rebase
    # Or reset
    git reset --hard origin/your-branch
  2. Continue — Return to the UI and click “Continue with local”.