One contract across platforms
The command surface remains consistent on Windows, macOS, and Linux while package managers and platform paths vary where necessary.
Qbit CLI installs system tools, runs repository workflows, and unifies Python, JavaScript, and Dart project management across Windows, macOS, and Linux.
The CLI documentation focuses on stable commands, package-manager detection, qbit.yml/qbit.toml configuration, language workflows, and the upgrade lifecycle.
Get the Windows, macOS, or Linux setup archive and install Qbit on your PATH.
Install tools through the native OS package manager and override the manager when required.
Define repeatable repository commands in qbit.yml or qbit.toml and execute them with qbit run.
Manage virtualenvs, JavaScript package managers, and dart pub through a consistent command surface.
Control install mappings, environment overrides, and qbit upgrade behavior through explicit contracts.
The stable release provides fixed archive names for all three operating systems. Installers, documentation, and the upgrader share those asset names as one release contract.
The command surface remains consistent on Windows, macOS, and Linux while package managers and platform paths vary where necessary.
Scripts and install mappings live in qbit.yml, qbit.yaml, or qbit.toml so project setup can be reproduced.
When a lockfile or override selects a package manager that is unavailable, Qbit returns an actionable error instead of silently switching managers.
Getting started, system packages, project scripts, Python, JavaScript, Dart, configuration, upgrade, and troubleshooting are available from the navigation.