tox CLI
The CLI creates Python environments and repeats project build, install and test steps for agent-led compatibility checks.
- 3,976 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- tox installs dependencies and runs project commands, which can access networks and modify files with process permissions.
Install
Manual install
Open the official tox installation guide linked from the README and follow the documented steps for the user’s system. Then inspect project commands, select the required environment and verify results without expanding into unreviewed commands.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- tox installs dependencies and runs project commands, which can access networks and modify files with process permissions.
This is third-party code. Review the repository files before installing.
What it does
tox manages separate environments for Python project checks. Users define interpreter versions, dependencies and commands, and an agent runs the agreed checks. This verifies package building, installation and tests across configurations. The project chooses its own test tools through configuration. The same workflow runs locally and in CI, with per-environment outcomes helping locate incompatible changes.
Who it is for. Python package authors supporting multiple configurations with consistent local and CI checks.
Good fit when
- A package must install and test under several Python versions.
- An agent fix needs the established project checks rerun.
- Local and CI test commands have diverged.
- Lint and test tasks need different environment dependencies.
Not a fit when
- You expect untrusted code to be isolated from the entire system.
- Required environment dependencies cannot be installed.
- Project configuration contains commands you cannot authorize.
Example request
Inspect tox configuration, run only the project test environment and explain any failure without changing settings.Limitations
The current source manifest requires Python 3.11 or later for tox itself, separately from test-environment requirements. Selected checks need available interpreters and dependencies before setup can complete. Configured commands run with process permissions; a virtual environment is not a security sandbox. Creating or rebuilding environments consumes storage and may contact package indexes, so check CI disk and network constraints.
How to disable. Stop tox and remove its CI invocation. Remove generated environments and caches separately after dependent processes finish.
FAQ
How do I list environments?
Use `tox list`.
How do I run one environment?
Pass the desired environment name after `tox run -e`, choosing it from `tox list`.
Where are commands defined?
In tox configuration, with dependencies and commands assigned to environments.
Is pytest mandatory?
No. tox runs the test tools chosen by the project.
Can the same workflow run in CI?
Yes. Aligning local and CI checks is a core purpose.
Discussion
No questions or reviews yet.
Related
CLI toolsMicrosoft’s CLI controls real terminal sessions, checks visible text and records test runs for investigating failures.
Venom runs YAML integration suites, executes HTTP requests and scripts, checks results and exports reports for CI.
Qlty CLI reports duplicate and complex code before refactoring; automatic formatting runs as a separate action.
MCP server, agent and skills for end-to-end UI tests where the agent drives the computer through vision on cloud machines
Corrections you give your agent turn into rule files in the repository and run with taskless check locally and in CI.
A CLI from TestMu AI that writes end-to-end tests from requirements and runs them in a browser or on mobile, with a skill for your agent
README in short
Beyond tests, tox checks package build and installation in selected environments, helping expose dependency incompatibilities.