Skip to content

docs(rfc): define deterministic agent plugin distributions - #1410

Open
PsiACE wants to merge 8 commits into
masterfrom
codex/agent-plugin-distributions-rfc
Open

docs(rfc): define deterministic agent plugin distributions#1410
PsiACE wants to merge 8 commits into
masterfrom
codex/agent-plugin-distributions-rfc

Conversation

@PsiACE

@PsiACE PsiACE commented Aug 31, 2026

Copy link
Copy Markdown
Member

Which issue or RFC does this PR close?

Refs #1405.

Rationale for this change

Shared Skills, MCP configuration, metadata, and names currently drift across host distributions. This RFC makes the existing Agent Plugin the canonical source and defines deterministic host projections without abstracting host-native lifecycle behavior.

What changes are included in this PR?

  • Add the English and Chinese Agent Plugin Distribution Architecture RFC.
  • Define source, target adapter, native runtime, and generated artifact ownership.
  • Specify build/check behavior, capability-manifest validation, naming, compatibility, migration, and drift prevention.

Are there any user-facing changes?

No. This PR records a design and does not change runtime behavior, installation paths, public APIs, or persisted formats.

How was this change tested?

  • uv run prek run --files docs/en/rfcs/1410_agent_plugin_distribution_architecture.md docs/zh/rfcs/1410_agent_plugin_distribution_architecture.md
  • make docs-test

AI usage statement

OpenAI Codex was used to inspect the existing Agent Plugin and related issues, draft the bilingual RFC, and run the listed validation commands.

@PsiACE
PsiACE marked this pull request as ready for review August 31, 2026 11:20

当前大多数 maintained Agent plugin 已经执行相同的 scope resolution、context preparation、Source capture、request budget、diagnostic 和 fail-open flow。这些是 PowerContext integration rule,不是宿主功能。公共逻辑已经足够明确,没有分别维护的理由。

宿主之间也确实存在差异。它们使用不同的 package layout、生命周期事件、payload、安装 API 和用户界面。Agent Plugins 统一了 Skills 和 MCP Server,但有意把 hook 和其他 client extension 留给宿主定义。因此,PowerContext 需要共享行为的公共来源和显式宿主映射,而不是一套通用宿主 API。

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently, different host support different abilities, just like #1416 mentioned, ref #1338. Should we align host plugins' ability before we design a public skill?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t think capability parity is a prerequisite. The public Skill should focus on how agents use the portable MCP surface. Shared code should provide only common client primitives, while host-specific behavior remains in downstream integrations.

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.

2 participants