We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Correct Execute threading and plugin root path API-Commands previously claimed Execute runs on the UI synchronization context. The host's CommandRunner uses TaskScheduler.Default and CommandRegistry awaits Execute with no UI marshaling — replace the claim with the actual thread-pool behavior and its two consequences. Debugging and Getting-Started described the plugin root as a per-user app-data path (%AppData%, ~/.config, ~/Library). The host actually resolves it as AppContext.BaseDirectory/plugins, next to the executable. Update the location, the post-build copy snippet, and the install example accordingly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Document plugin.json manifest and correct platform values Packaging-and-Distribution previously claimed there was no manifest format; the host actually requires a plugin.json read before the assembly is loaded. Add the full schema (sourced from PluginManifest.cs) and include the file in the build-output and folder-layout sections. Also correct the platform enumeration in Getting-Started: the host's PlatformMatches only accepts All/Windows/Linux, not macOS. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Plugin SDK Wiki