feat: add brand assets and Codex interface metadata - #3
Merged
Conversation
The plugin rendered in Codex with a generic pencil icon and "Website: Unavailable". Root cause: Codex takes presentation metadata from an `interface` object, not from the Agent Plugins `homepage` field, and the package shipped no interface object at all. Adds the Usable mark from the brand kit as assets/usable-icon.svg and assets/usable-logo.png (600x600), and declares interface metadata under extensions["com.openai"] — the namespace the spec sanctions for client-specific data, so the portable core stays untouched. Fields mirror what shipped Codex plugins use: display name, short/long description, developer, category, website, privacy and terms URLs, brand colour #347cbf (the site's theme_color), icon, logo, default prompt. URLs resolved rather than guessed: the apex domain 308-redirects to www, so homepage and the interface URLs use https://www.usable.dev to avoid a redirect hop. /privacy and /terms confirmed 200. Adding assets created two new failure modes, so both are now guarded: - assets/ added to the release archive allowlist, since the allowlist would otherwise silently drop them - the validator now checks client-extension file references are plugin-relative, contained within the plugin root, and actually exist. Verified by deleting the icon and watching validation fail. Three self-tests added (missing asset, path escaping root, non-reverse-domain namespace); suite is 18/18. SVG audited before asserting it is safe in the security docs: it contains only svg, g, path and ellipse elements, with no script, event handlers, href, xlink:href, foreignObject, use, or data: URIs. NOT VERIFIED: whether Codex reads the interface object from the inline com.openai extension. The CLI exposes no way to inspect resolved interface metadata, so this needs a look at the plugin UI. If it still renders unbranded, the documented fallback is a .codex-plugin/plugin.json overlay — which must be added carefully, because skill discovery works today and a malformed overlay could disturb it. Co-Authored-By: Oz <oz-agent@warp.dev>
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
1 participant
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.
Fixes the generic pencil icon and "Website: Unavailable" in the Codex plugin UI.
Root cause
Codex takes presentation metadata from an
interfaceobject — not from the Agent Pluginshomepagefield. The package shipped no interface object at all, so Codex had nothing to render and fell back to defaults.Change
assets/usable-icon.svg(composer icon) andassets/usable-logo.png(600×600).interfacemetadata underextensions["com.openai"]— the namespace the spec sanctions for client-specific data, so the portable core is untouched. Fields mirror shipped Codex plugins: display name, descriptions, developer, category, website, privacy/terms, brand colour#347cbf(the site'stheme_color), icon, logo, default prompt.URLs were resolved, not guessed: the apex domain 308-redirects to
www, so everything useshttps://www.usable.devto avoid a redirect hop./privacyand/termsconfirmed 200.Guards added
Adding assets created two new ways to ship something broken, so both are now closed:
assets/added to the release-archive allowlist — the allowlist would otherwise have silently dropped it, shipping a manifest pointing at files not in the tarball.Three self-tests added — missing asset, path escaping the root, namespace without a reverse domain. Suite is 18/18.
Security
Before asserting in
permissions-and-data-flow.mdthat the SVG is inert, I audited it. It contains only<svg>,<g>,<path>,<ellipse>— no<script>, event handlers,href,xlink:href,<foreignObject>,<use>, ordata:URIs.I could not verify this renders. Codex exposes no CLI surface for resolved interface metadata, and it writes no resolved manifest to disk — so the plugin UI is the only oracle and I can't see it.
The Codex PR that added Agent Plugins support states the inline
com.openaiextension is primary with.codex-plugin/plugin.jsonas a fallback overlay, which is why I used the inline form. Worth noting every shipped example I inspected uses the.codex-pluginfile instead.To check: reinstall and reopen the plugin detail view.
If it still renders unbranded, the fallback is a
.codex-plugin/plugin.jsonoverlay. That needs care: skill discovery works today, and a malformed overlay could disturb it — so it should be added with a re-check that both skills still reach the model.