What's New
Everything that shipped, and when
Releases and announcements read straight from the platform's own records, beside the latest from the blog, the gallery and the community. Nothing here is written to fill a space — where a source is quiet, it links to the page it belongs to.
From the blog
Field notes from the build- Fixing 400 Errors by Flattening Complex JSON Schemas: Deeply nested JSON schemas often trigger HTTP 400 errors during grammar compilation. Learn how flattening your object graphs preserves inference performance and prevents structural failures.
- Fixing Silent JSON Truncation in LLM Applications: Learn why setting max_output_tokens causes silent JSON corruption and how to build resilient, token-aware recovery logic. Discover strategies to prevent truncation before it compromises your production data.
- Stop Invaliding Your LLM Prompt Prefix Cache with Dynamic Schemas: Updating structured output schemas in agentic loops forces costly cache invalidation. Learn to use universal container schemas to keep your LLM performance fast.
In the gallery
Ranked by library useMost used
- COMPLETE and Reiterate as much work As possoble: 53 uses from its owner
- Resolve all identified issues: 44 uses from its owner
- Autonomous Bug Resolution Agent: 32 uses from its owner
- Technical Debt And Feature Roadmap Auditor: 19 uses from its owner
- Institutional Trading System Performance Audit: 14 uses from its owner
What the community is using
Reported working, then most copiedPlatform history
5 entries- FeatureMeasurement
First-use observations live
An account now joins the anonymous visitor row it grew out of, and the composer's first render and first interaction are recorded.
- The observations carry no prompt text — only that the composer rendered and that an intention began.
- Deliberately separate from commercial measurement, which this change leaves untouched.
- MilestoneMeasurement
Corrected commercial measurement live
The paid conversion now carries a transaction id, an internal purchase can no longer reach the ad account, and checkout was verified against the deployed runtime.
- Commercial figures measured before this moment came from the old instrument and are kept as historical evidence, never rewritten to conform.
- This date is never backdated.
- MilestoneMeasurement
Every pre-purchase path exercised against the deployed runtime
Each commercially important pre-purchase path was exercised against the deployed runtime rather than only in the editor.
- Visit, first generation, activation, trial isolation and anonymous-to-account merge were each confirmed live.
- Identity going live and identity being proven live are recorded as two separate moments, deliberately.
- ReleaseMeasurement
Commercial lifecycle deployed to production
The commercial lifecycle was confirmed live in production on every path, including a real successful generation.
- Visit, first generation, activation and anonymous-to-account merge each run end to end in production, not only in the editor.
- Records written before this instant are kept as historical evidence but are not counted against the health of the current deployment.
- MilestoneMeasurement
First-party visitor identity goes live
Visitor and person counts recorded before this moment were measured under the legacy address-derived model, and are not directly comparable with anything after it.
- A visitor is now identified by a first-party id this app issues, stable across visits on that browser and carrying no personal information.
- One address can no longer stand in for several people, and one person is no longer split by changing address.