Skip to content

🤖 docs: RFC for Mux plugins and marketplaces#3485

Open
dcieslak19973 wants to merge 5 commits into
coder:mainfrom
dcieslak19973:rfc/plugins-marketplaces
Open

🤖 docs: RFC for Mux plugins and marketplaces#3485
dcieslak19973 wants to merge 5 commits into
coder:mainfrom
dcieslak19973:rfc/plugins-marketplaces

Conversation

@dcieslak19973
Copy link
Copy Markdown

Summary

Adds an RFC (rfc/20260607_plugins-and-marketplaces.md) proposing a Mux plugin + marketplace system: a declarative, vendor-neutral plugin bundle that packages Mux's existing extension primitives (skills, hooks, MCP servers, agents, commands) and a marketplace to distribute/install/version/trust them as a unit.

Background

Mux already supports the individual primitives but configures each independently — there's no way to bundle, distribute, or version a coherent set. The ecosystem has converged on a declarative-bundle-plus-marketplace model (Claude Code and Codex share nearly the same manifest shape; opencode took a code-module + npm route). This RFC documents that prior art and proposes a Mux design that reuses its existing loaders and trust model.

What's in the RFC

  • Prior-art comparison of Claude Code, Codex CLI, and opencode plugin/marketplace systems, with the spec-level differences that matter for the design.
  • Vendor-neutral layout: .agents/plugin.json + .agents/plugins/marketplace.json (matching Codex's neutral namespace), while accepting .claude-plugin/.codex-plugin for import compatibility. Resolved installs + trust state stay Mux-owned under ~/.mux/ (the same split Codex uses) so a trust grant to one agent doesn't implicitly authorize another.
  • Component mapping onto Mux's existing skills/hooks/MCP/agents loaders.
  • Cross-tool hook coverage table (mux 4 · Codex 10 · Claude Code 31 · opencode ~30) plus a prioritization of which events to add first, framed around Mux's parallel worktree-lane lifecycle (Stop, worktree teardown, Pre/PostCompact, SessionStart resume, UserPromptSubmit), and the structured decision protocol as a prerequisite.
  • Trust/security model built on policyService + runtime isolation as a differentiator.
  • Phasing from declarative-only loading → marketplace/install lifecycle → trust-gated hooks/MCP.

Docs-only; no code changes. Intended as a planning artifact for review and steering.


Generated with mux • Model: claude-opus-4-8

dcieslak19973 and others added 5 commits June 7, 2026 15:28
Scopes a declarative plugin bundle (.mux-plugin/plugin.json) + marketplace
aligned to the Claude Code / Codex convention, mapping components onto Mux's
existing skills/hooks/MCP/agents, with a trust model built on policyService.
Includes a spec-level comparison of Claude Code, Codex CLI, and opencode.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adopt .agents/plugin.json and .agents/plugins/marketplace.json (matching
Codex's vendor-neutral namespace) instead of a mux-branded .mux-plugin dir;
keep resolved installs + trust state mux-owned under ~/.mux. Canonical hook
env is ${AGENT_PLUGIN_ROOT} with ${CLAUDE_PLUGIN_ROOT} alias.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Frame which events to add first around mux's parallel-lane lifecycle (Stop,
worktree teardown, compaction, resume), call out the worktree-teardown gap,
and note the structured JSON decision protocol as a Phase 3 prerequisite.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant