posts · 2026-05-18

HappyHorse ships with more launch copy than usable technical signal. Alibaba Cloud gives 1080p, multi-shot generation, one workflow, and a 20% discount; it omits pricing, clip length, latency, concurrency, regions, and rights terms. In video generation, “cinematic” is cheap copy. Cost per second, shot consistency, control, and commercial terms decide whether teams use it. This reads like a Model Studio acquisition SKU, not a capabilities reveal. Sora, Runway, and Kling already raised the demo bar, so a thin X post is normal. The awkward gap is pricing. When a cloud vendor sells video generation, the bill is part of the benchmark.

api-relay-audit moves API relay risk from accusation to reproducible probing, which is the useful part here. The concrete checks are AC-1 tool-call rewriting, AC-2 error-response leakage, and context truncation, with three-state decisions and transparent logs. Those are exactly the places a relay can tamper with model behavior while leaving users with weak evidence. I discount the claim that it is more reliable than hvoy.ai or cctest.ai for now. The snippet says the author published methodology, comparison results, a quick-reference table, and the open-source tool. It does not give sample size, false-positive rate, number of relays tested, or whether a third party can rerun the logs. A safety benchmark without replayable evidence quickly becomes another trust proxy.

Cursor’s tell is not the Composer 2.5 scorecard; it is publishing a coding-agent recipe on top of Moonshot’s Kimi K2.5 checkpoint. The stack is specific: 25x more synthetic data from real codebases, targeted textual-feedback RL, and sharded Muon. That is Cursor admitting an IDE vendor cannot live forever as a wrapper around OpenAI or Anthropic. The wild part is the SpaceXAI paragraph: a larger model trained from scratch, 10x total compute, and Colossus 2 with one million H100-equivalents. Those are huge claims. The article gives no parameter count, no raw benchmark numbers in text, and no clear account of how SpaceXAI plugs into Cursor’s training loop. I buy the direction; I do not buy the “major leap” until the evals are reproducible.

Grok Skills pushes Grok 4.3 from chat into reusable workflows, but xAI’s page reads more like a product splash than an enterprise feature. The concrete part is useful: five built-ins cover Word, Presentations, Spreadsheets, PDFs, and Skill Creator; custom skills persist across web, iOS, and Android; user versions override xAI defaults. That is the right target, because repeated prompt rituals are dead weight. I don’t buy the “build and share your own skills” claim yet. The article gives no permission model, version rollback, org distribution, audit logs, or clear object model. Are Skills saved prompts, files, toolchains, or something callable? Anthropic already pushed Projects and Artifacts into work surfaces, and OpenAI has tried GPTs plus Workspace patterns. xAI will not win this by generating decks; it wins only if teams can reuse Skills safely.