How jev-preview differs from jev-latest, and why selecting Jev 1.14 does not itself enable images or long context.
TypeSafe AI announced Jev 1.14 on October 14. A migration involves two separate choices: the model version and permission to use experimental capabilities.
On October 19, the model documentation still maps jev-latest to jev-1.13.0 and jev-preview to jev-1.14.0. The announcement promises a latest update after a week; that is a plan, not evidence of a completed switch. A versioned ID and the response’s model field help track a controlled migration.
Images require TypeSafe-Danger-Zone-Images: true on each relevant request. Both versions support images, while the Box type, which returns an image region, requires 1.14. The vendor explicitly says these capabilities are not production-ready.
Long context has a separate switch: TypeSafe-Danger-Zone-Long-Context: true. The documentation warns of reduced accuracy and speed. Changing versions therefore does not replace evaluating experimental modes on your own tasks. NODVIEW compared the announcement and documentation; we did not test the API or response quality.