@essentialai/cogent-bridge 3.19.0 → 3.19.2

package/CHANGELOG.md

@@ -1,5 +1,40 @@
 # Changelog
 
+## 3.19.2 — 2026-08-13
+
+### Fixed — Codex plugin cold-starts instantly (zero-dependency `npx` package)
+- **Follow-up to 3.19.1.** The npx fix in 3.19.1 worked once `npx` was warm, but a **cold** first
+  install lacked the cogent tools for ~10 s: `npx @essentialai/cogent-bridge` installs the full
+  package's runtime deps (nodemailer, imapflow, ws, MCP SDK…), which can exceed Codex's short
+  plugin-MCP startup window on a cold machine. Proven on Mac (`codex plugin add` → first cold session
+  `COGENT_TOOL_MISSING`; warm → `OK`).
+- **Fix:** new **zero-dependency** npm package `@essentialai/cogent-bridge-bundled` whose `bin` **is**
+  the self-contained bundle (`cogent-bridge.mjs`, all deps inlined by esbuild). `codex-plugin/.mcp.json`
+  now runs `npx -y @essentialai/cogent-bridge-bundled@<version>`. With no dependencies to install,
+  cold `npx` just fetches one ~250 kB tarball and runs (~2–3 s) → fits Codex's window → cogent tools
+  present on the **first** turn, even cold. Kept in lockstep with the bridge by the build
+  (`scripts/build-bundle.mjs` copies the bundle into the package) + a release-skill assert.
+- Functionally identical to `@essentialai/cogent-bridge` (same bridge, same version). Claude Code's
+  `plugin/.mcp.json` still uses the bundled `${CLAUDE_PLUGIN_ROOT}` form. Bridge `src/` unchanged.
+
+## 3.19.1 — 2026-08-13
+
+### Fixed — Codex plugin now launches the bridge via `npx` (the bundled path never worked on Codex)
+- **The real "codex cogent pain" — `⚠ MCP client for cogent failed to start … connection closed:
+  initialize response` — is fixed.** The Codex plugin's `.mcp.json` ran
+  `node ${CLAUDE_PLUGIN_ROOT}/bridge/cogent-bridge.mjs`, but **Codex 0.147 does not implement the
+  Agent Plugins spec for a plugin-bundled stdio MCP server**: it does not substitute `${PLUGIN_ROOT}`
+  in `args`/`cwd`, does not inject `PLUGIN_ROOT`/`PLUGIN_DATA` into the MCP child's env, and does not
+  resolve a `./`-command against the plugin root. It passed `${CLAUDE_PLUGIN_ROOT}/…` **literally** as
+  a relative arg (joined to the user cwd) → `MODULE_NOT_FOUND` → the server never started. Proven on a
+  Mac and on Linux (isolated `CODEX_HOME` trace) — cross-confirmed independently by a Codex-side peer.
+- **Fix:** `codex-plugin/.mcp.json` now uses a **bare command** — `npx -y @essentialai/cogent-bridge@3.19.1`
+  — which is spec-conformant and needs no `PLUGIN_ROOT`. Verified on Codex 0.147: warm start → bridge
+  ready ~2 s, native `cogent_*` tools available. (Claude Code's `plugin/.mcp.json` keeps the bundled
+  `${CLAUDE_PLUGIN_ROOT}` form, which Claude Code expands correctly.)
+- **Bridge `src/` is byte-identical to 3.19.0** — the version bump keeps the plugin-pin lockstep and
+  cache-busts the Codex `npx` pull. No relay/wire change.
+
 ## 3.19.0 — 2026-08-13
 
 ### Security — a cloud-configured agent that has not joined a channel no longer touches host-global local state

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@essentialai/cogent-bridge",
-  "version": "3.19.0",
+  "version": "3.19.2",
   "description": "MCP server for inter-Claude-Code session communication bridge",
   "type": "module",
   "workspaces": [

package/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.eaisdevelopment/cogent",
   "title": "Cogent Bridge from Essential AI Solutions (essentialai.uk)",
   "description": "MCP bridge for inter-session communication between Claude Code instances",
-  "version": "3.19.0",
+  "version": "3.19.2",
   "repository": {
     "url": "https://github.com/eaisdevelopment/cogent",
     "source": "github"
@@ -12,7 +12,7 @@
     {
       "registryType": "npm",
       "identifier": "@essentialai/cogent-bridge",
-      "version": "3.19.0",
+      "version": "3.19.2",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"