<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Hotfix Daily</title>
<link>https://hotfixdaily.com/</link>
<description>Hotfix Daily is a free weekday email for people who build with AI: five things worth your attention in AI, AI agents, vibe coding, and game dev, plus one tip to try today. About a 3-minute read.</description>
<language>en-us</language>
<atom:link href="https://hotfixdaily.com/rss.xml" rel="self" type="application/rss+xml"/>
<lastBuildDate>Wed, 21 Oct 2026 11:00:00 +0000</lastBuildDate>
<item>
<title>Hotfix Daily #1: Mercury 3, Voxtral 3, Beacon and more</title>
<link>https://hotfixdaily.com/issues/001/</link>
<guid isPermaLink="true">https://hotfixdaily.com/issues/001/</guid>
<pubDate>Wed, 21 Oct 2026 11:00:00 +0000</pubDate>
<description><![CDATA[<article class="item"><h2><span class="n">1</span> Inception ships Mercury 3, a diffusion model built for speed</h2>
<p>Mercury 3 drafts the whole response at once and then refines it, instead of writing one token at a time. On Inception's own benchmarks it beat GPT-6 Luna and Claude Haiku 5.5 on 8 of 12 tests at 1,068 tokens/sec, and it has a 1M-token context. No one outside the company has published results yet.</p>
<p class="why"><strong>Why builders care:</strong> It is on OpenRouter and Vercel, and OpenAI-API code needs only minor changes, so testing it is cheap.</p>
<p class="src"><a href="https://siliconangle.com/2026/10/20/inception-says-mercury-3-beats-gpt-6-luna-and-claude-haiku-5-5-at-up-to-8x-the-speed/" rel="noopener">Source</a></p>
</article>
<article class="item"><h2><span class="n">2</span> Mistral launches Voxtral 3 and a voice agent SDK</h2>
<p>New speech-to-text and text-to-speech models plus an SDK built on LiveKit. It runs listening, reasoning, tool calls, and speech as one streaming pipeline, and Mistral says each turn finishes in under a second. It works over WebRTC in browsers and over SIP for phone calls.</p>
<p class="why"><strong>Why builders care:</strong> Voice agents used to mean wiring three vendors together. Now it's one SDK priced per minute, and you can still swap out the LLM.</p>
<p class="src"><a href="https://mistral.ai/news/voxtral-3/" rel="noopener">Source</a></p>
</article>
<article class="item"><h2><span class="n">3</span> Beacon: shared memory for your coding agents</h2>
<p>Asymptote Labs raised a $5.5M seed round for Beacon, an MIT-licensed open-source layer. It records sessions across Claude Code, Codex, Cursor, and 20+ other agent tools, and it lets lessons from earlier sessions carry over instead of disappearing.</p>
<p class="why"><strong>Why builders care:</strong> If you hop between Cursor and Claude Code, you can stop re-explaining your project to each one.</p>
<p class="src"><a href="https://www.asymptotelabs.ai/blog/asymptote-labs-raises-5-5m-seed-round" rel="noopener">Source</a></p>
</article>
<article class="item"><h2><span class="n">4</span> Game studios use AI everywhere, but not deeply</h2>
<p>Vivrato interviewed 101 studio leaders: 94% use AI in at least one production stage, yet 52% rate how deeply it's built into their pipeline at 3/10 or lower. European studios reported deeper adoption than North American ones.</p>
<p class="why"><strong>Why builders care:</strong> The gap is in the pipeline. Studios have picked up AI tools but haven't built them into how they work, and that's an opening for tools that fit real game dev workflows.</p>
<p class="src"><a href="https://gamesbeat.com/adam-boyes-vivrato-issues-report-based-on-101-game-leaders-views-on-ai-in-gaming-exclusive/" rel="noopener">Source</a></p>
</article>
<article class="item"><h2><span class="n">5</span> Repo of the day: Google's Harness²</h2>
<p>This trending open-source framework (Apache 2.0) improves the setup around an agent while the agent works: prompts, memory, tools, skills, and subagents. The model itself stays the same. Google reports gains of up to 11.5 points on WorkBuddy-Bench. It supports OpenCode and Codex as executors.</p>
<p class="why"><strong>Why builders care:</strong> You can get better results by improving the setup around your model, without switching to a new one.</p>
<p class="src"><a href="https://github.com/google-research/harness2" rel="noopener">Source</a></p>
</article>
<aside class="tip"><h2>🛠 Try this today</h2>
<p>Before you accept "done" from your coding agent, make it <strong>show proof</strong>: run the tests, the build, or a screenshot. Then have a fresh-context subagent review the diff. The Claude Code team says that's the first layer of their review process. From June to September, their merged PRs more than doubled while the share needing reverts fell by over 40%. Put your run-able checks in a short <code>CLAUDE.md</code> (or <code>.cursorrules</code>).</p>
<p class="src"><a href="https://claude.dev/blog/solving-code-review-at-anthropic/" rel="noopener">Source</a></p>
</aside>
]]></description>
</item>
</channel>
</rss>
