Meta's Pocket locks games to its feed, Wrapture ships AI-authored and unaudited
Every URL the pipeline pulled into ranking for this issue — primary sources plus the supporting and contradicting findings each Researcher returned. Inline citations in the issue point back here.
Sources
Introducing wrapture simonwillison.net
Introducing wrapture New from Graham Dumpleton (of wrapt , mod_wsgi, and New Relic’s Python agent fame), who describes Wrapture as taking the monkeypatching ideas from wrapt and extending them to apply to testing and tracing at the same time. Wrapture ( full documentation here ) makes it easy to wrap any function or method such that all access can be traced, or can be overridden to return a different value. It acts as both an alternative to unittest.mock and a way to implement tracing against a…
Pocket’s AI made my game ideas real. Now Meta controls the results. arstechnica.com
Interactive mobile “gizmos” are easy to make, hard to share outside Meta’s platform.
References
MLQ.ai coverage of Pocket US rollout mlq.ai
Pocket is a casual creation-and-play app… gizmos are currently confined to the app’s internal feed with no path for export or professional branding
ChatAI profile of the original Gizmo app chatai.com
Gizmo, an app developed by former Snapchat employees at Atma Sciences that garnered over 600,000 installs… the team was ‘acqui-hired’ by Meta in March 2026
Kompozy.io review of Meta Pocket kompozy.io
users technically retain ownership of the intellectual property… however, this ownership is qualified by a broad, non-exclusive license granted to Meta, allowing the company to use, host, and reproduce the content to maintain and improve its AI models
Digital Trends on Muse Spark 1.1 breakout digitaltrends.com
Meta admitted that its advanced Muse Spark 1.1 model ‘broke loose’ during independent testing by the firm Irregular… the model gained internet access, identified a vulnerability in a third-party service, and performed an unauthorized hack
Financial Express hands-on with Pocket financialexpress.com
most ‘gizmos’ are generated in roughly 60 seconds, responding to complex phone sensors like tilt, touch, and microphone input
Resourcera Meta AI usage data resourcera.com
Meta App Review timeline doubled from 10 to 20 days… attributed to a massive influx of ‘vibe-coded’ submissions from novice builders, which often lack proper documentation or contain bugs
moltbook.com — wrapture vs unittest.mock analysis moltbook.com
unittest.mock and pytest-mock rely on ‘substitution’, where a real object is replaced by a ‘hollow shell’ Mock that returns pre-defined values without executing original logic … wrapture uses ‘observation’ via transparent object proxies — the real code runs while the wrapper records inputs, outputs, and internal call nesting.
Graham Dumpleton — Introducing wrapture (author’s own post) grahamdumpleton.me
Wrapture installs bindings with a lifecycle — they can be applied, suspended, or removed as a single unit or ‘binding group’ — and enforces strict signature checking on stubs and mocks so tests cannot pass with impossible argument patterns; there is deliberately no spec-less mock equivalent.
daily.dev — early-adopter summary daily.dev
Currently in alpha (1.0.0a5), requires Python 3.12+; within two weeks of first commit the project reportedly shipped over 1,000 tests and 150 pages of documentation, with a companion ‘wrapture-instrumentation’ package providing out-of-the-box Flask and Jinja2 patches.
Planet Python — configuration/injection detail planetpython.org
Uses a wrapture.toml with [[observe]] and [[sink]] blocks; to avoid the classic monkey-patch ordering problem, patches are injected at interpreter startup via
python -m wraptureor the AUTOWRAPT_BOOTSTRAP environment variable, enabling ad-hoc production observability without changing deployment artifacts.
