JEV GUIDE

Jev 1.14 update: model selection, images and Box localization

Reviewed against official documentation on October 15, 2026. Model availability, SDK releases and community-project compatibility are separate questions. We have not benchmarked the model.

Jev Gallery · Reviewed 2026-10-15

Choose the model deliberately

Jev 1.14 became available October 14. jev-preview points to jev-1.14.0; jev-latest still points to jev-1.13.0. Both cost $0.042 per million input tokens, with free output. Pin versions for reproducibility and record the response model.

Source: TypeSafe · Models ↗

Images remain experimental

Images are off by default. Both 1.13 and 1.14 require TypeSafe-Danger-Zone-Images: true. Assets can supply images in state, instructions or criteria. TypeSafe describes them as dreamer-ready, not production-ready; formats, limits and accuracy may change.

Source: TypeSafe · Images ↗

A Box does not prove the target exists

Box requires jev-1.14.0 or jev-preview. Each question returns one rectangle with normalized top, bottom, left and right edges plus confidence. It has no not-found result. Pair it with a Noul presence check before using its coordinates.

Source: TypeSafe · Box ↗

Enable long context separately

Defaults are 64k per request and 32k per question. On both versions, TypeSafe-Danger-Zone-Long-Context: true raises both to 262k. The documented token price is unchanged, but processing is slower and less accurate.

Source: TypeSafe · Models ↗

JavaScript SDK 0.7.0 migration

Released October 14, version 0.7.0 requires Node.js 22+, stops exporting request payload types, and adds images and Box. On Node.js 22.15+, bodies of at least 1 KiB use zstd by default; compression: false disables it. Check runtime and type imports first.

Source: TypeSafe · JavaScript SDK changelog ↗

Python SDK 0.7.5 and gateways

Python 0.7.5 adds Image, Box and attach_assets, with zstd request compression enabled by default. Its changelog warns that unofficial APIs may not support compression immediately. Validate SDK, model and gateway changes separately.

Source: TypeSafe · Python SDK changelog ↗

Our suggested migration sequence

Run the same business samples against old and new configurations, record errors, fallback behavior, latency and cost, then recalibrate thresholds. Newly curated projects are not automatically verified for 1.14; their pages retain the model and dependency boundaries of the reviewed source.

Keep image and Box experiments reversible; coordinates are not proof of a correct action target.
Test missing images, absent targets, failed requests and low-confidence results.
Retain the previous configuration and original evidence until the new behavior is accepted.