Pyvider 0.6.2 contains one focused development-mode fix.
Fixed
The wrapper created by pyvider install no longer changes into the provider checkout before starting the provider. Terraform launches providers as subprocesses, and the inherited working directory is part of its path contract. Preserving it keeps path.module, path.root, bare relative paths such as ./file, and the default .pyvider/state filesystem state root anchored to the practitioner’s working directory.
The provider’s own configuration no longer depends on that directory change. When the checkout contains pyvider.toml, the wrapper pins it explicitly through PYVIDER_CONFIG_FILE, separating provider configuration from Terraform-relative path resolution.
See the Pyvider v0.6.2 release for the canonical release record.