Way forward for open-plugin-spec

[cloud-on-prem]

Hi team,

First off, amazing work on this! I would love to see open-plugin-spec adopted as an industry standard.

Are you already engaging with the major harness vendors? If so, do you see any interest on their end in solidifying this as an open standard?

For context, my motivations are tied to my own open-source project: https://github.com/rp1-run/rp1.

Even if the vendors do not move forward at this point, I am very tempted to build a cross-harness extractor based on this spec to support my project.

Please let me know if there is anything I can do to contribute. I would love to get your thoughts on the best way forward!

[fboldo]

Hi @cloud-on-prem and Open Plugin Spec team,

I've released https://github.com/fboldo/oiap (MIT licensed) in the last couple of days as a TypeScript SDK to write AI agent plugins once and export to multiple agent harnesses.

I'm also interested to know about vendor adherence. I believe projects like OIAP will emerge as frameworks and abstractions, but the final output will eventually become the Open Plugin Spec.

[unional]

Hi @fboldo,

I'm interested in working on a similar project.
But my approach is more language agnostic and declarative in nature.

I have my rough idea here: https://github.com/cyberuni/cyber-universal-agent-plugin/blob/main/spec/universal-plugin-system.md

Would you like to work on at together? Either in that project or in your project are good for me.

[mquadrat]

Seems like Goose is adopting it, which would be huge as it's an AAIF project. But other than that I haven't found a lot of mentions in the wild yet.