Repository navigation
Add optional publisher policy URLs to the plugin manifest - #96
Open
digitarald wants to merge 1 commit into
Open
digitarald wants to merge 1 commit into
digitarald wants to merge 1 commit into
Conversation
A plugin's privacy policy and terms of service describe the plugin as distributed rather than the client that loads it, so clients and catalogs otherwise rediscover the same information through client-specific extensions. Add optional `privacyPolicyUrl` and `termsOfServiceUrl` fields to the plugin manifest so an author can declare them once. Both fields are validated only by their JSON types, matching the treatment of `homepage`, `repository`, and `author.url`: a malformed policy link is not fatal to an otherwise valid plugin. HTTPS is recommended, not required. Clients may present the URLs and are not required to retrieve or display them. A client that presents them attributes them to the plugin publisher, since the fields do not describe independently operated services that a plugin accesses. Closes #92 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
digitarald
force-pushed
the
agent/policy-urls
branch
from
November 13, 2026 05:42
654e1d2 to
44a0ff8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds optional
privacyPolicyUrlandtermsOfServiceUrlfields toplugin.jsonin Agent Plugins 1.1.0, so a plugin author can declare the publisher's policies once instead of through a client-specific extension.Motivation
The manifest carries portable publisher metadata such as
homepage,repository, andlicense, but has no field for a privacy policy or terms of service. Both are commonly required when plugins are distributed through marketplaces or enterprise catalogs, and the information is not client-specific: it describes the plugin as distributed, regardless of which client loads it.Authors already publish these URLs in spec-conformant manifests by placing them in a client namespace. In
obsidianmd/obsidian-skills,reactive-resume, andpascalorg/editor, the manifest declaresagent-plugins.org/schemas/1.0.0and carries the policy URLs underextensions["com.openai"].interface. Clients that read a different namespace cannot see them. Cursor and Kiro both load spec-conformant plugins and define no equivalent fields of their own, so their users have nowhere portable to put this today.The field names already exist in native manifests. Claude Code reads
privacyPolicyUrlandtermsOfServiceUrlfrom the top level of its plugin manifest, as indocker/skills. Codex readsprivacyPolicyURLandtermsOfServiceURLfrom its owninterfaceobject.Proposal
{ "$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json", "name": "example-plugin", "privacyPolicyUrl": "https://example.com/privacy", "termsOfServiceUrl": "https://example.com/terms" }The fields identify the publisher's own privacy policy and terms of service, and do not describe independently operated services that a plugin accesses. Clients may present them and are not required to retrieve or display them. A client that presents them attributes them to the plugin publisher. HTTPS is recommended.
The names follow the top-level form Claude Code already reads, which is also the casing used in the wider plugin ecosystem. No alias is defined for Codex's nested, differently cased fields, which remain part of that client's own namespace.
Rationale
Like the other metadata URLs, both fields are validated only by their JSON type. Requiring a URL form or an HTTPS scheme would make a malformed policy link fatal to an otherwise valid plugin, which is a worse outcome than a link a client can decline to present. A wrong JSON type remains fatal, as for every other recognized field.
Attributing the URLs to the publisher keeps their scope accurate without requiring a client to verify legal documents or identify who operates a service a plugin reaches.
This PR defines no relationship between the portable fields and any client namespace that carries similar data. Each client continues to own the contents and interpretation of its own extension namespace.
Compatibility
The change applies only to the 1.1.0 working draft; the published 1.0.0 specification remains unchanged. The fields are optional and additive, so existing conforming manifests stay valid and clients that do not implement them are unaffected.
Closes #92.