boring-plugin-build

To architect a workspace extension for Boring UI, determine the optimal registration path for your panels and commands based on trust requirements and deployment scope. The plugin architecture validates manifest configuration and wires up trusted backend routes within the Pi harness ecosystem.

Choosing between a runtime plugin and an app-internal package depends on your deployment scope. Runtime or generated plugins suit rapid prototyping, while app-internal packages are optimal for shipping production-ready workspace features and trusted backend routes.

Registering trusted backend routes for agent tools in the Pi harness requires selecting the correct plugin registration path based on your specific trust requirements. This process ensures proper manifest configuration and wires backend routes directly into the Boring UI ecosystem.

Verify your Boring UI plugin integration for production deployment by running standardized checklists that enforce type checking, linting, and proper manifest configuration rules. This validation ensures your workspace extension is correctly structured and registered.

Yes, you can use generated plugins for rapid prototyping in the Boring UI workspace. This architecture path facilitates fast iteration before transitioning to app-internal packages for shipping production-ready features and finalizing manifest configuration.