Installing extensions
Choose the right package type, inspect compatibility, and use the matching desktop installation workflow.
On this page
The PlayWeld marketplace distributes free packages. The IDE's editor extensions, platform plugins, skills, and agent roles have different purposes and installation contracts.
Identify the package before downloading
| Package type | Purpose |
|---|---|
| Editor extension | Editor capabilities packaged as VSIX |
| Platform plugin | Executable contributions through the platform plugin manifest and runtime |
| Skill | Task instructions and referenced resources |
| Agent role | A focused responsibility and associated skills and access ceilings |
Read the listing's publisher, license, declared compatibility, support link, release notes, and package details. A declared version range and a valid archive do not prove runtime compatibility with every Theia or PlayWeld build.
Follow the desktop workflow
Download a published release and use the instructions for its type. Platform plugin archives are handled by their installation controls; skills and roles use their supported local installation or authoring paths. Do not rename one kind of package to make it look like another.
Direct installation from the website into the desktop is planned. This marketplace currently provides package downloads, not a one-click editor registry integration.
Review privileges and trust
For an executable plugin, inspect capabilities and runtime prerequisites before accepting installation. For a skill, read its instructions and origin; project-local instructions require the relevant trust decision. Installation does not itself authorize every operation described in a guide.
Use plugin capability review or skills and roles for more detail.
Verify the outcome
Check the selected project's activation state and the specific contributed capability. If a package cannot run, inspect compatibility, missing prerequisites, and the recorded runtime error. Keep the release version and error when contacting its publisher. Website package checks validate archive structure and metadata; they are not malware scanning or a runtime acceptance test.