Unified · Split
| @@ -0,0 +1,25 @@ | |||
| 1 | --- | ||
| 2 | "executor": minor | ||
| 3 | "@executor-js/plugin-mcp": minor | ||
| 4 | "@executor-js/sdk": minor | ||
| 5 | --- | ||
| 6 | |||
| 7 | Add locally installed OpenAI Codex plugins as one-click integrations: Messages | ||
| 8 | (iMessage/SMS), Chrome, Computer Use, Computer History, and OpenAI Developer | ||
| 9 | Docs. They appear in the connect dialog with their own icons, and a card that | ||
| 10 | cannot run yet says what to install and links to it. | ||
| 11 | |||
| 12 | Tool calls reach the plugins through `codex app-server` rather than a plugin's | ||
| 13 | own MCP server, because their services only honour calls from a Codex host | ||
| 14 | session. Computer Use and Chrome ship no MCP server at all, so their APIs are | ||
| 15 | projected as typed tools — `list_apps`, `click`, `read_page`, `navigate` — that | ||
| 16 | compile to a single call each. No model turn is involved; nothing is bundled or | ||
| 17 | downloaded, and a machine without Codex simply sees the setup steps. | ||
| 18 | |||
| 19 | A plugin's own approval prompt now reaches the caller, and states the terms it | ||
| 20 | carries: a browser prompt that persists for a site says so. Approvals are asked | ||
| 21 | once per session rather than per call. | ||
| 22 | |||
| 23 | Elicitation requests can carry implementation-defined metadata through | ||
| 24 | `FormElicitation` / `UrlElicitation`, and a paused execution reports it. Both | ||
| 25 | fields are optional and additive. | ||