docs/PYPI_INSTALLATION.md
The easiest way to run LangBot is using uvx (recommended for quick testing):
uvx langbot
This will automatically download and run the latest version of LangBot.
You can also install LangBot as a regular Python package:
# Using pip
pip install langbot
# Using uv
uv pip install langbot
Then run it:
langbot
Or using Python module syntax:
python -m langbot
When published to PyPI, the LangBot package includes the pre-built frontend files. You don't need to build the frontend separately.
When running LangBot as a package, it will create a data/ directory in your current working directory to store configuration, logs, and other runtime data. You can run LangBot from any directory, and it will set up its data directory there.
LangBot supports the following command line options:
--standalone-runtime: Use standalone plugin runtime--debug: Enable debug modeExample:
langbot --debug
If you want to contribute or customize LangBot, you should still use the manual installation method by cloning the repository:
git clone https://github.com/langbot-app/LangBot
cd LangBot
uv sync
cd web
npm install
npm run build
cd ..
uv run main.py
To update to the latest version:
# With pip
pip install --upgrade langbot
# With uv
uv pip install --upgrade langbot
# With uvx (automatically uses latest)
uvx langbot
When running LangBot from the PyPI package (via uvx or pip), there are a few behavioral differences compared to running from source:
Version Check: The package version does not prompt for user input when the Python version is incompatible. It simply prints an error message and exits. This makes it compatible with non-interactive environments like containers and CI/CD.
Working Directory: The package version does not require being run from the LangBot project root. You can run langbot from any directory, and it will create a data/ directory in your current working directory.
Frontend Files: The frontend is pre-built and included in the package, so you don't need to run npm build separately.
These differences are intentional to make the package more user-friendly and suitable for various deployment scenarios.