Skip to content

Image Context Runtime v0.2.0

Latest
Latest

Choose a tag to compare

View all tags
@shixinnt shixinnt released this 15 Aug 09:37
v0.2.0
b067f0e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Image Context Runtime v0.2.0

v0.2.0 lets multiple Codex tasks using the same fixed configuration share one authenticated loopback Broker and one durable Runtime worker. It keeps Provider concurrency, idempotency, output reservations, and restart reconciliation under a single owner instead of treating another task's live Job as interrupted.

Highlights

  • authenticated IPv4-loopback Broker with bounded unauthenticated time, per-client in-flight work, response buffering, and stdio backpressure
  • race-safe concurrent Broker autostart and owner-checked descriptor cleanup
  • conservative shutdown recovery: a forced interruption after Provider dispatch becomes needs_review and is never automatically repeated
  • cursor-based bounded Job history
  • dry-run-first terminal Job compaction with retired idempotency tombstones
  • conservative server/discover response without claiming full MCP 2026-07-28 conformance
  • updated doctor, architecture, security, privacy, troubleshooting, claims, and validation documentation

Install

git clone --depth 1 --branch v0.2.0 https://github.com/shixinnt/codex-image-context-runtime.git
cd codex-image-context-runtime
codex plugin marketplace add .
codex plugin add codex-image-context-runtime@codex-image-context-runtime
npm run configure -- --workspace "C:\path\to\your\project" --provider mock

Upgrade from v0.1.1

Stop active image jobs, update the clone, then refresh the plugin cache:

git fetch --tags
git checkout v0.2.0
codex plugin remove codex-image-context-runtime@codex-image-context-runtime
codex plugin add codex-image-context-runtime@codex-image-context-runtime

External configuration and Runtime data are preserved by reinstalling the plugin. Restart Codex after the update.

Validation and boundaries

The offline release gates passed on Windows, Ubuntu, and macOS with Node.js 22, plus Ubuntu with Node.js 24. Isolated fresh-install and v0.1.1-to-v0.2.0 upgrade checks passed. See docs/validation-v0.2.0.md for the receipt.

The Broker is same-user local coordination, not a sandbox against another process running as the same operating-system user. Automated retention policy, secure erasure, full MCP 2026-07-28 conformance, and Tasks interoperability are not claimed in v0.2.0. No live Provider calls were used for release validation.

Assets 4
Loading