🧪 Upcoming Feature: Zippy Plugin System (EDIT: v0.2.0 released and this feature is now available for everyone🥰)
Status: Currently in testing
Goal: Empower users to extend Zippy without modifying its core source code
Feature Available Version: Currently planned to release this feature with zippy v0.2.0
🔧 What’s Coming
We’re working on a modular plugin system for Zippy that allows users to build and install their own features as standalone executables. These plugins will integrate seamlessly with Zippy’s CLI, enabling advanced functionality while keeping the core lightweight.
🚀 Key Highlights
-
No need to modify Zippy’s source code
You can build plugins independently using Go or any language that compiles to a CLI binary.
-
Secure execution
Official Plugins will only run when invoked through Zippy, using internal checks like:
- Environment token validation
- Parent process verification
- Optional manifest-based metadata
-
Simple installation
Users will be able to install plugins via copying plugins executable to zippy's installed directory. (Also we planned add zippy install command too)
-
Clean invocation
Once installed, plugins can be run like native Zippy commands:
-
Custom functionality
Examples include:
- Exporting Zippy versions to Git commits
- Generating changelogs
- Integrating with external tools
🧩 Plugin Structure (Preview)
Each plugin will be a standalone executable with:
- A secure entry point
- Optional manifest file for metadata
- Internal checks to prevent unauthorized execution
🛡️ Why This Matters
This system gives users the freedom to:
- Extend Zippy for their own workflows
- Share plugins with others
- Keep the core tool fast, focused, and stable
💬 Feedback Welcome
If you have ideas for plugin use cases, security concerns, or CLI design preferences, feel free to comment below or open a discussion thread. Your input will help shape this feature!
🧪 Upcoming Feature: Zippy Plugin System (EDIT: v0.2.0 released and this feature is now available for everyone🥰)
Status: Currently in testing
Goal: Empower users to extend Zippy without modifying its core source code
Feature Available Version: Currently planned to release this feature with zippy v0.2.0
🔧 What’s Coming
We’re working on a modular plugin system for Zippy that allows users to build and install their own features as standalone executables. These plugins will integrate seamlessly with Zippy’s CLI, enabling advanced functionality while keeping the core lightweight.
🚀 Key Highlights
No need to modify Zippy’s source code
You can build plugins independently using Go or any language that compiles to a CLI binary.
Secure execution
Official Plugins will only run when invoked through Zippy, using internal checks like:
Simple installation
Users will be able to install plugins via copying plugins executable to zippy's installed directory. (Also we planned add zippy install command too)
Clean invocation
Once installed, plugins can be run like native Zippy commands:
Custom functionality
Examples include:
🧩 Plugin Structure (Preview)
Each plugin will be a standalone executable with:
🛡️ Why This Matters
This system gives users the freedom to:
💬 Feedback Welcome
If you have ideas for plugin use cases, security concerns, or CLI design preferences, feel free to comment below or open a discussion thread. Your input will help shape this feature!