pipx CLI
The manager installs Python applications into separate environments and exposes commands for users and terminal agents.
- 12,987 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installation downloads executable packages whose commands run with normal user permissions.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/pipxDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installation downloads executable packages whose commands run with normal user permissions.
This is third-party code. Review the repository files before installing.
What it does
pipx installs Python command-line applications with dependencies in separate environments. An agent can prepare a tool list for a user to install without mixing dependencies across applications. After PATH setup, their commands run from the normal shell. The manager lists, upgrades and uninstalls applications. `pipx run` uses a temporary environment for one-off use. It manages end-user CLI tools, while development-project dependencies remain part of the project’s own setup.
Who it is for. Python CLI users adding several tools to agent workflows without one shared dependency environment.
Good fit when
- An agent task needs a packaged Python command.
- Two applications require conflicting library versions.
- An application needs a one-off trial without a permanent app installation.
- A user wants to upgrade and remove CLI tools independently.
Not a fit when
- The package is needed as an importable project library.
- You need a security boundary isolating untrusted code from files and networks.
- Downloading and running the selected package is not permitted.
Example request
Identify the Python CLIs required and propose pipx installations without changing the current project’s dependencies.Limitations
pipx targets applications with command entry points; importable project libraries belong in the project environment. Separate dependencies do not restrict an application’s access to user files or networks. The app-command directory must be on PATH or the shell will not find installed tools. The current source package requires Python 3.11 or newer, while individual managed applications can have their own interpreter requirements.
How to disable. Uninstall unwanted applications through pipx, then remove the manager and PATH integration if needed. Application-created data requires separate removal.
FAQ
Must I activate an environment for every command?
No. Once PATH is configured, application commands are directly available.
What does `pipx ensurepath` do?
It makes the application-command directory available to the shell.
How do I try an application once?
Use `pipx run` with the chosen application.
Is this a security sandbox?
No. The executed application retains normal user permissions.
Can I manage application updates?
Yes. pipx lists, upgrades and removes packages it manages.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI manages Python projects, environments and package builds so agents can run repeatable repository-defined commands.
APM
APM (Agent Package Manager)
A package manager for AI agent context: skills, prompts and MCP servers install with one command across supported agents
Python runtime for agent work: task boundaries, independent verification of results and a saved handoff between sessions
An extension for the Pi coding agent that folds tool calls into compact lines and renders file edits as readable diffs
The tty7 skill teaches Claude Code and Codex to drive tty7 terminal panes: run commands in a real PTY, read the screen and hand work to another agent
Ix turns a repository into a persistent graph of symbols, calls and imports, and Claude Code or Codex query the structure through MCP
README in short
When available, uv handles installation; otherwise pip is used. The manager runs with regular user permissions.