Thanks for helping improve PlatformIO workflows in Zed.
- Keep the project open source and editor-agnostic where possible.
- No
.env-driven configuration model. - No private machine config, hidden automation scaffolding, or personal files in the published repo.
- Prefer small, readable Rust over clever abstractions.
- Every integration decision should map back to documented Zed or PlatformIO behavior.
- If Zed does not support something today, document the limitation instead of faking parity with VS Code.
- Keep the project clearly marked as unofficial and not affiliated with PlatformIO Labs or Zed Industries.
- Minimize magic.
- Prefer transparent
piocommand generation over wrappers that hide behavior. - Keep PlatformIO parsing and task generation independently testable.
- Avoid unnecessary dependencies.
cargo test
cargo fmtTo test against a PlatformIO project:
cargo run --bin platformio-for-zed -- --project-dir /path/to/project --backup --with-clangd- Tests pass with
cargo test - Code is formatted with
cargo fmt - README/docs are updated when behavior changes
- No generated binaries, logs, personal paths,
.envfiles, or machine-local config are committed - Zed and PlatformIO limitations are documented honestly
- New UX claims are backed by Zed API docs or working code
Please include:
- Zed version
- PlatformIO Core version (
pio --version) - operating system
- relevant
platformio.ini - generated
.zed/tasks.jsonif applicable - exact command and output