Skip to main content
Bugster CLI generates and runs AI-powered end-to-end tests for web applications.

​
Requirements

Node.js 18+

Required for browser automation

GLIBC 2.35+

Required for Linux distributions
Operating Systems:
  • macOS (compatible)
  • Linux: Ubuntu 22+, Ubuntu 24+, Debian 12+, and any distribution with GLIBC ≥ 2.35
  • Windows (compatible)

Next.js

Pages and App Router supported.

React.js

React Router DOM v6/v7 supported.

Framework Compatibility Details

View detailed framework support and routing compatibility information
Coming Soon: Vue, Angular

Vercel

Vercel deployments compatible.

Railway

Railway deployments compatible.

Netlify

Netlify deployments compatible.

​
Installation

  • macOS / Linux
  • Windows

​
Automated Installation

curl -sSL https://bugster.dev/install.sh | bash

​
Reset your terminal session

After installation, make sure to reset your terminal so PATH changes take effect. You can either close and reopen your terminal, or run:
source ~/.zshrc   # zsh
source ~/.bashrc  # bash

​
Verify Installation

bugster --version

​
Troubleshooting

node --version  
# Should show v18.0.0 or higher

ldd --version
# Should show GLIBC 2.35 or higher
Symptom: Installation fails with permission errors, even when using sudo.Cause: The ~/.local directory may have been created by another process with root ownership, preventing your user from writing to ~/.local/bin.Solution:
1

Check directory ownership

ls -ld ~/.local ~/.local/bin
If the owner is root instead of your username, proceed to the next step.
2

Fix ownership

sudo chown -R $(whoami) ~/.local
3

Retry installation

Run the installer again without sudo:
curl -sSL https://bugster.dev/install.sh | bash
Alternative solution: Install directly to /usr/local/bin:
# Download the binary manually first, then:
sudo cp bugster /usr/local/bin/
If you encounter compatibility issues on Linux, ensure your distribution has GLIBC 2.35 or higher. Supported distributions include Ubuntu 22+, Ubuntu 24+, Debian 12+, and other modern distributions.
Symptom: After running the installer, bugster.exe is not found in the installation directory (%LOCALAPPDATA%\Programs\bugster), or it disappears shortly after installation.Cause: Because the executable is downloaded from the internet and is not digitally signed by a major publisher, Windows Defender or other antivirus software may automatically quarantine or delete it as a security precaution.Solution:
1

Check Protection History

  1. Open Windows Security > Virus & threat protection.
  2. Go to Protection history to see if bugster.exe was quarantined. If so, you can restore it and allow it on your device.
2

Add an Exclusion

To prevent this from happening in the future, add an exclusion:
  • Under Virus & threat protection settings, click Manage settings.
  • Scroll down to Exclusions and click Add or remove exclusions.
  • Click Add an exclusion, select Folder, and paste the following path: %LOCALAPPDATA%\Programs\bugster
Symptom: After a successful installation, you type bugster --help and get an error like 'bugster' is not recognized....Cause: The terminal session where you ran the installer has an old copy of the PATH variable. The changes made by the installer will only be loaded by new terminal sessions.Solution: Close your current terminal window and open a new one. The command should now work correctly.
What gets installed: Bugster CLI, Playwright browsers, and all required dependencies are installed automatically. Python is no longer required for Bugster versions > 0.3.26.

Get Started

Follow our quickstart guide to set up your first project