March 30, 2026 in announcements, plugins by Alex2 minutes
Since the last release, I’ve been working on enhancing the plugin ecosystem, and I’m excited to announce that v0.5.0 is now live!
Regarding the plugin architecture, AWF now leverages go-plugin, gRPC gateway, and Protobuf. Plugins can now expose operations, commands (step-types), and validators. This move provides a more flexible architecture and a significantly better user experience across the ecosystem.
Manage AWF plugins: list, enable, and disable plugins.
Plugins extend AWF functionality by providing custom operations,
commands, and validators.
Examples:
awf plugin list
awf plugin enable slack-notifier
awf plugin disable slack-notifier
Usage:
awf plugin [command]
Aliases:
plugin, plugins
Available Commands:
disable Disable a plugin
enable Enable a plugin
install Install a plugin from GitHub releases
list List all available plugins
remove Remove an installed plugin
search Search for available plugins on GitHub
update Update an installed plugin to the latest versionPlugin examples are available in the AWF repository. I also wrote a simple one, time, specifically to help our beloved LLMs handle time. The documentation has been updated and can be found here.
This release was important to me because, while plugins are not mandatory to use AWF, they are essential if you want to avoid writing overly long script files when interacting with other services.
I hope you enjoy this new feature!
I developed a github action that allows you to run workflows directly in your CI/CD pipelines. This is particularly useful for providing rich context to an agent when creating PRs in other repositories (e.g., for documentation).
I’m not using this action myself just yet, but I plan to integrate it as soon as I merge the PR for the CLI-associated skills.
It took a whole week, but I finally caved and bought a domain! It’s just a webpage for now, but it’s a start.
While attending Symfony Live, Nicolas convinced me to give a lightning talk about AWF. Here are the slides:
The primary focus for the next release will be workflows. I want to refine this feature and enable workflow sharing. This community-driven approach is a priority for me, as it will significantly improve the experience for everyone.
I’ve been digging through my archives and found two other projects that I plan to integrate with the CLI. The goal is to build a truly deterministic ecosystem for AWF.
I hope you’re ready to read some Zig!