Desktop appCurrent v0.5.0

Pyenv Native

A native desktop and command-line way to install, switch, and manage Python versions.

  • Desktop app
  • Command line
  • MCP server
Get the current build View source on GitHub
Works on
  • Windows
  • macOS
  • Linux
  • Android (experimental)
Current packaged builds
  • Linux
  • macOS
  • Windows
Latest
v0.5.0
Released
Oct 12, 2026
Language
Rust
Current files
6 direct
Pyenv Native runtime manager workspace.
Native Python runtime manager with installed versions, environments, and setup controls.
Download · current stable release

Download for your system

Oct 12, 2026

Choose your operating system, then select the package or architecture that matches it. Every download goes straight to the current release asset.

Versionv0.5.0
Direct files6
Platforms3

Windows

2 build options
02
Windows x64Download pyenv-gui-windows-x64.exe19 MBChecksum
Windows ARM64Download pyenv-native-windows-arm64.zip7.6 MBChecksum

macOS

2 build options
02
macOS Apple SiliconDownload pyenv-gui-macos-arm6421 MBChecksum
macOS IntelDownload pyenv-gui-macos-x6423 MBChecksum

Linux

2 build options
02
Linux x64Download pyenv-gui-linux-x6425 MBChecksum
Linux ARM64Download pyenv-native-linux-arm64.tar.gz9.0 MBChecksum

Checksum or signature files are linked beside the matching GitHub asset.

Open the release history on GitHub
Other entry points

Use the operating-system installer from the current release, open a new terminal, then run `pyenv doctor`. The README documents the shell and Termux differences.

Read the install instructions
The point of it

What it does

Developers and coding agents managing multiple Python versions across Windows, Linux, macOS, and experimental Termux builds.

It handles runtime installs, shims, local and global selection, virtual environments, and an optional GUI without asking every project to reinvent shell setup.

  • Install the native manager for the current operating system, then run `pyenv doctor`.
  • Install a Python runtime, select it globally or per project, and create a named virtual environment.
  • Use the GUI when a visual runtime inventory is more useful than a terminal-only workflow.
  • Use `pyenv-mcp` for agent-assisted environment resolution only after the target project is understood.
Open the project README