Danger zone

TypeSafe's release philosophy splits reliability from experimentation: features it considers too jagged for production ship behind headers like TypeSafe-Danger-Zone-Images: true and TypeSafe-Danger-Zone-Long-Context: true, while stable behavior stays default. The company says the features will persist on future models and improve, but warns builders use them at their own risk.

For a builder the header is a contract marker: a request that needs one is explicitly outside the reliability bar, its format and limits can change between releases, and TypeSafe's own docs tell you to prototype rather than deploy. It also gives a clean migration path — when a feature graduates, the header disappears and the same call shape becomes default.