Desktop install
macOS
Choose the latest Apple Silicon or Intel DMG, then complete the unsigned app first-run steps below if macOS blocks the app.
Downloads resolve to the latest published release automatically.
PyVessel runs locally on macOS, Windows, and Linux. Download the latest build from the install buttons below, complete the platform-specific first-run steps, and make sure the VS Code and Zed CLI commands are available on PATH.
We will try to detect the right platform automatically, or you can choose a build below.
macOS note
Unsigned app guidance is included below.
Editor launch
Install the code and zed CLIs before relying on editor launch from PyVessel.
Each button resolves to the latest matching release asset automatically. Pick the artifact that matches your operating system, then follow the notes below.
Desktop install
Choose the latest Apple Silicon or Intel DMG, then complete the unsigned app first-run steps below if macOS blocks the app.
Downloads resolve to the latest published release automatically.
Desktop install
Download the latest Windows installer or MSI package, then launch PyVessel locally with your normal user account.
Downloads resolve to the latest published release automatically.
Desktop install
Pick the latest AppImage, .deb, or .rpm build, make it executable if needed, and start using PyVessel for local Python projects.
Downloads resolve to the latest published release automatically.
This is the section people should actually follow on macOS. It is short on purpose and written for the real first-run flow.
Download the latest macOS build from the install buttons on this page.
Open PyVessel once from Finder.
If macOS blocks the app, open System Settings > Privacy & Security and choose Open Anyway.
If Finder still blocks the app, try right-click > Open to reveal the allow dialog.
PyVessel can launch editors for the active project, but it depends on the CLI command being installed on PATH or the app being discoverable on your machine.
code .sudo ln -s /Applications/Zed.app/Contents/MacOS/zed /usr/local/bin/zed
Linux users can link the installed zed binary into
/usr/local/bin if needed, then verify with
zed .
The current app may be unsigned. Launch it once, then use System Settings > Privacy & Security > Open Anyway. If that does not appear, try right-click > Open on the app bundle.
Open VS Code, launch the Command Palette, and run Shell Command: Install 'code' command in PATH. Open a new terminal session and verify with code .
Use Zed’s built-in CLI install flow if available. Otherwise add the zed binary to PATH manually, then open a fresh terminal and verify with zed .
Editor launching depends on the CLI command being installed on PATH or the app being discoverable on your machine. Confirm code and zed work directly in a terminal before testing the launch action again.
The guide stays practical on purpose: install the app, handle the macOS first-run prompt if needed, and make sure code and zed work in a terminal.