Enhance distribution system with npm packages and marketplace

[darrenhinde]

Overview

Improve the distribution and installation system by creating npm-publishable packages for plugins and building a marketplace/registry for community-contributed agents and context.

Goals

• Create npm-publishable packages for plugins
• Build plugin/preset marketplace/registry
• Add /import-preset command for bundle installation
• Improve collision detection and merge strategies
• Implement version management for installed presets
• Enable community-contributed agents and context
• Document distribution and publishing workflows

Key Features

NPM Packages

• Publish plugins as npm packages
• Scoped packages (@openagents/plugin-name)
• Semantic versioning
• Dependency management
• Installation via npm/yarn/pnpm

Marketplace/Registry

• Central registry of available plugins
• Search and discovery
• Ratings and reviews
• Version compatibility tracking
• Download statistics

Import System

• /import-preset command for quick installation
• Bundle installation (multiple components)
• Dependency resolution
• Conflict detection and resolution

Collision Handling

• Improved merge strategies
• Interactive conflict resolution
• Backup and rollback support
• Diff visualization

Version Management

• Track installed preset versions
• Update notifications
• Upgrade/downgrade support
• Compatibility checking

Community Contributions

• Plugin submission process
• Quality guidelines
• Review and approval workflow
• Featured plugins

Package Structure

@openagents/plugin-name/
├── package.json
├── .opencode-plugin/
│   └── plugin.json
├── commands/
├── agents/
├── skills/
└── README.md

Related

• Current install.sh and registry.json system
• Plugin system architecture

Success Criteria

• NPM package structure defined
• At least 1 plugin published to npm
• Marketplace/registry implemented
• Import command functional
• Collision handling improved
• Version management working
• Publishing workflow documented
• Community guidelines created

[Tim-Rambo]

You could take a look at the, OCX project.

I feel like OCX is the perfect devtool for testing out new features and additions to OAC. Just install the OAC dev profile and you gucci, seems like OCX is going to create a registry for profiles themselves. 👀

You could have Dev profile installed at X and have Y as the main driver, does changes to OAC and you can test the new changes right away, without no configuration hassle to worry about.

OCX OpenCode extension manager with portable, isolated profiles. Your setup, anywhere.

[darrenhinde]

Thanks for this, it’s very close to how I picture it.
We need a modular system that allows users to download and manage packages and components.

Honestly didn’t think about the profiles sections so this is a good addition to think about how to allow users to have different settings and components based on their profile.

Do need to take care of over doing things as this could be a deep hole to go under.

Do you want either make your own version or use this as the add on for the mod? What are your thoughts?

[Tim-Rambo]

Maybe copy what OCX architecture, and incorporate it only as a OAC plugins/mod/preset tool?
Since overall OAC is a framework that builds on top of OC after all, and maybe want to create a OAC ecosystem? Maybe also add OAC in OCX for simple installation too?