Skip to content

Commands & tasks ​

Command palette ​

CommandIDDoes
PyPilot: Set Up Environmentpypilot.setupBuilds the environment, installing Python if needed (uv mode), and installs the dependencies. Same as pypilot setup.
PyPilot: Doctor: Show Environment Reportpypilot.doctorRuns the health check and opens the report.
PyPilot: Fix Python Versionpypilot.fixPythonRebuilds the environment on a supported Python. Same as pypilot fix python.
PyPilot: Fix CUDA / PyTorch Buildpypilot.fixCudaRe-pins torch/tensorflow to the build for your driver. Same as pypilot fix cuda.
PyPilot: Check Package Compatibility…pypilot.checkAsks for a package (or requirement) and adds a pypilot check section to the report.
PyPilot: Install Package…pypilot.installAsks for a package, installs it and records it in the manifest.
PyPilot: Update Bundled Data Tablespypilot.updateDataRefreshes the CUDA, framework and import tables now.
PyPilot: Migrate Conda environment.yml to pyproject.tomlpypilot.migrateCondaSame as pypilot migrate-conda.
PyPilot: Open Environment Report Panelpypilot.openReportRuns the health check and opens the report (in the webview panel 1.3).
PyPilot: Install uv Globallypypilot.installUvInstalls uv so it is available outside this workspace too.
PyPilot: Check for Helper Updatespypilot.updateHelperOffers the pinned engine version when it is newer than the engine in use; with pypilot.engineUpdates: "latest", also newer releases. (1.2.1 and older compare against the latest GitHub release.)
PyPilot: Use Project Environment (.venv / pixi)pypilot.useProjectVenvMakes the project environment the active interpreter.
PyPilot: Install pixi 1.3pypilot.installPixiCliInstalls pixi with its official installer, through the engine; with an older engine it offers to run the installer in a terminal.
PyPilot: Initialize pixi project 1.3pypilot.initPixiProjectOpens the engine's full pixi.toml preview beside the editor, then asks write pixi.toml as shown in the preview? (Write pixi.toml or Write and run pixi install). Nothing is written before you choose.

Every command that changes the environment shows a progress notification and updates the status bar from the result; a failed setup is reported as a failure.

Hidden where they do not apply 1.3 ​

Project-specific commands are hidden from the palette where they cannot apply. They still run from the walkthrough, keybindings and the report panel.

CommandShown only whenContext key
Fix CUDA / PyTorch Builda manifest (pyproject.toml, requirements*.txt, pixi.toml, environment.yml) names torch or tensorflowpypilot.hasTorch
Migrate Conda environment.yml to pyproject.tomlan environment.yml (or .yaml) existspypilot.hasCondaEnv
Install pixipixi is not on PATH or in ~/.pixi/bin!pypilot.pixiInstalled
Initialize pixi projecta folder is not a pixi project yetpypilot.hasNonPixiProject

The context keys can be used in your own keybindings' when clauses too.

Tasks ​

Tasks: Run Task → pypilot lists tasks that run the CLI in the integrated terminal, so you see streaming output. You can also declare them in tasks.json:

json
{
  "version": "2.0.0",
  "tasks": [
    { "type": "pypilot", "task": "setup", "label": "pypilot: setup" },
    { "type": "pypilot", "task": "doctor", "label": "pypilot: doctor" }
  ]
}
taskRuns
setuppypilot setup
doctorpypilot doctor
fix pythonpypilot fix python
fix cudapypilot fix cuda
update-datapypilot update-data
migrate-condapypilot migrate-conda

The notification ​

On open, one notification at most. Fix environment runs the same code as pypilot setup; Show details opens the report; Ignore dismisses it; Never for this project is remembered in .zed/pypilot.toml as [state] never = true. With engine support for the pixi advisory, an Initialize pixi project button appears when pixi would help. That button is handled by the engine, not by the palette command: it shows one message with what pixi.toml would contain and the buttons Write and install, Write pixi.toml and Cancel (see From the editor). How often you are notified is set by pypilot.notifications.

When uv is missing in auto mode, Fix environment first offers to install it (about 18 MB, once, globally) and asks whether to use a uv project (pyproject.toml + lockfile) or the pip-compatible mode (requirements.txt, faster through uv). No thanks continues with pip.

Engine: AGPL-3.0-or-later. Zed and VS Code extensions: Apache-2.0. pypilot-cli: AGPL-3.0-or-later.