Codex adds use-case gallery and official plugins for shadcn/ui and Box
OpenAI published a Codex use-case gallery with one-click workflows, and shadcn/ui and Box shipped official plugins. Teams can now install reusable app and web workflows directly instead of wiring each integration by hand.
TL;DR
- OpenAI added Codex plugins as installable bundles of apps and skills, letting the agent pull in external app context instead of staying confined to the editor, according to Codex plugins and a practitioner breakdown of how those bundles work across surfaces plugin breakdown.
- OpenAI also published a one-click Codex use-case gallery that opens runnable workflows inside Codex for jobs like building iOS apps, analyzing datasets, and generating reports and slides use-case gallery.
- Two official plugins were called out on launch day: shadcn/ui for web app building shadcn plugin and Box for automating workflows around Box content Box plugin.
- Early user reaction is less about novelty than consolidation: developers say they can now “live in Codex” while plugins handle cross-tool work such as Linear triage and broader Vercel workflows Linear workflow Vercel reaction.
What did OpenAI actually ship?
Codex plugins are the new packaging layer. The launch post says they are “combinations of Apps and Skills” Codex plugins, while plugin breakdown adds the implementation detail that a plugin can bundle app connections, reusable workflows, and optional MCP servers into one installable unit.
That matters because OpenAI paired the packaging change with a new use-case gallery inside Codex. OpenAI’s developer account says those workflows open “in one click in the Codex app” and cover concrete tasks such as building iOS apps, analyzing datasets, and generating reports and slides use-case gallery. The result is a more opinionated starting point: instead of wiring tools one by one, teams can start from a prebuilt workflow and then swap in the plugins they need.
Which plugins landed first, and how are people using them?
The clearest launch-day examples were official plugins for shadcn/ui and Box. The shadcn/ui post says the library “now ships in the official Codex plugin for building web apps” and can be added from the Plugins menu shadcn plugin. Separately, the Box announcement says teams can take “any content within Box” and automate workflows around it inside Codex Box plugin.
Supporting posts fill in the early usage pattern. One user said the Linear plugin is already turning “noisy” work into Codex-managed flow Linear workflow. Another said it is “way more fun to just live in codex” while plugins handle “work comms between tools,” and specifically pointed to a Vercel plugin covering that ecosystem Vercel reaction. Taken together, the immediate shift is not a new model capability but a broader execution surface: Codex can now carry context and actions across product, content, and frontend systems with installable packages instead of custom glue.