Skip to content

v1.1.2 — the wrappers actually run now

Latest

Choose a tag to compare

@Sateezg Sateezg released this 09 Aug 09:02
· 2 commits to main since this release

1.1.1 and earlier do not work on current Codex builds. Both wrappers failed before doing anything. If you installed this plugin and it told you to log in when you were already logged in, this is why.

Fixed

Every command failed with "codex is not logged in", even when logged in.
codex login status writes its result to stderr. The precondition check was codex login status 2>/dev/null | grep -qi 'logged in' — which discards the very output it greps for, so it never matched and both wrappers exited 1 immediately. The check now uses the exit status (0 logged in / 1 logged out). That also closes the inverse bug: grep -i 'logged in' matched "Not logged in" too, so a genuinely logged-out user would have been waved straight through to a confusing downstream failure.

--ref was completely broken — every edit and style-locked generation failed.
Codex's -i/--image <FILE>... flag is variadic, so it swallowed the trailing prompt as one more image filename. Codex found no prompt, fell back to reading one from stdin, and exited 1 with No prompt provided via stdin. The prompt is now passed after a -- separator. codex-run got the same separator, so a task that begins with a dash can no longer be parsed as a flag.

Marketplace manifest failed validation. The root-level description key belongs under metadata. claude plugin validate now passes on both the plugin and the marketplace manifest.

Added

  • test/smoke.sh — a dependency-free regression guard for both bugs above. No network, no Codex quota. Run it before every release.
  • assets/ — the README demo GIF, a style-locked icon set, and the social preview card. Every one of them was generated by this plugin, and assets/README.md has the exact commands and the VHS tape so you can reproduce them.

Upgrading

/plugin update codex-bridge

Already-installed copies under ~/.claude/plugins/ carry their own copy of the wrappers, so an update is required — patching the repo alone won't fix a local install.