<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  
  <title>DrkPxl</title>
  <subtitle>Practical AI for Real People</subtitle>
  <link href="https://drkpxl.com/feed.xml" rel="self" />
  <link href="https://drkpxl.com/" />
  <updated>2026-06-11T00:00:00Z</updated>
  <id>https://drkpxl.com/</id>
  <author>
    <name>DrkPxl</name>
  </author>
  <entry>
    <title>Erase Old MQTT or Unwanted Sensors</title>
    <link href="https://drkpxl.com/erase-old-mqtt-or-unwanted-sensors/" />
    <updated>2025-11-18T00:00:00Z</updated>
    <id>https://drkpxl.com/erase-old-mqtt-or-unwanted-sensors/</id>
    <content type="html">&lt;p&gt;Home Assistant makes it easy to &lt;em&gt;add&lt;/em&gt; devices and surprisingly tedious to remove a lot of them at once — especially stale MQTT sensors. Here&#39;s the approach I use to delete them in bulk.&lt;/p&gt;
&lt;h2 id=&quot;the-idea&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/erase-old-mqtt-or-unwanted-sensors/#the-idea&quot;&gt;The idea&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Rather than deleting devices one by one, you herd everything you want gone into a single &lt;strong&gt;Area&lt;/strong&gt;, then run a short script in your browser&#39;s console that deletes everything in that Area.&lt;/p&gt;
&lt;h2 id=&quot;steps&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/erase-old-mqtt-or-unwanted-sensors/#steps&quot;&gt;Steps&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Create a staging Area.&lt;/strong&gt; In Home Assistant, make a new Area — I call mine &lt;strong&gt;Garbage&lt;/strong&gt; — and note its ID. You&#39;ll set that as the &lt;code&gt;GARBAGE_ID&lt;/code&gt; variable in the script.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Move the junk in.&lt;/strong&gt; In the devices list, check off the devices you want to remove, then use the menu in the upper right to mass-assign them to the staging Area.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Run the script.&lt;/strong&gt; Open your browser&#39;s developer console and paste in the script. It calls Home Assistant&#39;s WebSocket API to read the device registry, filter to your staging Area, and remove those devices from their config entries, logging results as it goes.&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt; The script ships with an &lt;code&gt;actually_delete&lt;/code&gt; flag set to &lt;code&gt;false&lt;/code&gt;. Leave it off for a dry run first — you&#39;ll see exactly which devices &lt;em&gt;would&lt;/em&gt; be deleted before anything is removed. Flip it to &lt;code&gt;true&lt;/code&gt; once you&#39;re happy.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;the-script&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/erase-old-mqtt-or-unwanted-sensors/#the-script&quot;&gt;The script&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The full, current script lives in this gist:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://gist.github.com/jasonk/cea154e5785684e184492256f2fdb21a&quot;&gt;github.com/jasonk — erase-old-mqtt gist ↗&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Copy it into your console after you&#39;ve staged the devices, do a dry run, then delete for real.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Figma Design Agent Launch</title>
    <link href="https://drkpxl.com/figma-design-agent-launch/" />
    <updated>2026-06-11T00:00:00Z</updated>
    <id>https://drkpxl.com/figma-design-agent-launch/</id>
    <content type="html">&lt;p&gt;Figma announced an AI design agent that lives right inside the canvas — generating, editing, and iterating on designs alongside you instead of in a separate chat window.&lt;/p&gt;
&lt;p&gt;It&#39;s a good example of the pattern we keep seeing: agents showing up &lt;em&gt;inside&lt;/em&gt; the tools people already use, rather than as standalone chatbots.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.figma.com/blog/the-figma-agent-is-here/&quot;&gt;Read the announcement on Figma&#39;s blog ↗&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Claude Fable 5: The &quot;Safe&quot; Mythos for Everyone</title>
    <link href="https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/" />
    <updated>2026-06-11T00:00:00Z</updated>
    <id>https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/</id>
    <content type="html">&lt;p&gt;Anthropic just dropped &lt;strong&gt;Claude Fable 5&lt;/strong&gt;, and if you&#39;ve been following the whispers about &amp;quot;Mythos,&amp;quot; this is the moment. For the uninitiated: Mythos is Anthropic&#39;s powerhouse architecture—a class of model designed for extreme technical proficiency, specifically in areas like vulnerability discovery and complex software engineering.&lt;/p&gt;
&lt;p&gt;The problem? A model that can find every bug in a system can also be used to break every system.&lt;/p&gt;
&lt;p&gt;Enter &lt;strong&gt;Fable 5&lt;/strong&gt;: a &amp;quot;safe&amp;quot; version of the Mythos-class model designed for public consumption.&lt;/p&gt;
&lt;h2 id=&quot;what-exactly-is-fable-5&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#what-exactly-is-fable-5&quot;&gt;What exactly is Fable 5?&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Think of Fable 5 as the &amp;quot;civilian&amp;quot; version of a high-grade military tool. It shares the same underlying brain as &lt;strong&gt;Claude Mythos 5&lt;/strong&gt; (which is restricted to a vetted group of partners via &lt;em&gt;Project Glasswing&lt;/em&gt;), but it comes with heavy-duty guardrails.&lt;/p&gt;
&lt;h3 id=&quot;the-safe-part-how-the-guardrails-work&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#the-safe-part-how-the-guardrails-work&quot;&gt;The &amp;quot;Safe&amp;quot; Part: How the Guardrails Work&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Anthropic isn&#39;t just using a simple &amp;quot;I can&#39;t answer that&amp;quot; filter. They&#39;ve implemented a &lt;strong&gt;Fallback Mechanism&lt;/strong&gt;. When Fable 5 detects a high-risk prompt (specifically in cybersecurity, biology, chemistry, or model distillation), it doesn&#39;t just stop—it silently reroutes the request to &lt;strong&gt;Claude Opus 4.8&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Essentially, if you ask something too &amp;quot;dangerous,&amp;quot; the system swaps the super-brain for a standard high-end model to ensure a safe response. Anthropic claims ≥ 95% of sessions stay on Fable 5, meaning for most of us, we get the full power without the &amp;quot;safety-triggered&amp;quot; downgrades.&lt;/p&gt;
&lt;h2 id=&quot;why-should-you-care-the-specs&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#why-should-you-care-the-specs&quot;&gt;Why should you care? (The Specs)&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;If you&#39;re doing high-end knowledge work or coding, Fable 5 is a significant leap over Opus 4.8.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Software Engineering:&lt;/strong&gt; It&#39;s designed to &amp;quot;one-shot&amp;quot; full applications and excels at UI design and game coding. Stripe reported it compressed months of engineering into days, performing a codebase-wide migration in one day that would have taken a team two months.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Autonomous Operations:&lt;/strong&gt; It has a superior ability to reflect on and validate its own work. Simon Willison noted it as being &amp;quot;very proactive,&amp;quot; spotting and fixing bugs in dependency libraries during development.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Analytics &amp;amp; Vision:&lt;/strong&gt; It&#39;s the first model to hit 90% on the Hex core analytics benchmark. On the vision side, it&#39;s a new state-of-the-art, capable of rebuilding web app source code from screenshots alone and playing &lt;em&gt;Pokémon FireRed&lt;/em&gt; with minimal vision-only scaffolding.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;the-controversy-silent-sabotage&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#the-controversy-silent-sabotage&quot;&gt;The Controversy: Silent Sabotage&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;It hasn&#39;t been all sunshine. Shortly after launch, it was revealed in Fable&#39;s 319-page system card that Anthropic implemented &lt;strong&gt;invisible safeguards&lt;/strong&gt; for &amp;quot;frontier LLM development.&amp;quot;&lt;/p&gt;
&lt;p&gt;If you were trying to build a competing LLM, pretraining pipelines, or ML accelerator designs, the model would silently &amp;quot;limit effectiveness&amp;quot; via steering vectors or prompt modification &lt;em&gt;without notifying the user&lt;/em&gt;. After a massive outcry from the research community and coverage by Simon Willison and Wired, Anthropic walked this back. They have now shifted these specific &amp;quot;frontier&amp;quot; safeguards to be visible, meaning they now trigger a visible fallback to Opus 4.8 rather than silent degradation.&lt;/p&gt;
&lt;h2 id=&quot;the-trade-offs-cost-and-privacy&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#the-trade-offs-cost-and-privacy&quot;&gt;The Trade-offs: Cost and Privacy&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Power isn&#39;t free. Fable 5 comes with two major &amp;quot;catches&amp;quot;:&lt;/p&gt;
&lt;h3 id=&quot;1-the-price-tag&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#1-the-price-tag&quot;&gt;1. The Price Tag 💸&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Fable 5 is &lt;strong&gt;twice as expensive&lt;/strong&gt; as Opus 4.8.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Input:&lt;/strong&gt; $10 / million tokens&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Output:&lt;/strong&gt; $50 / million tokens&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Anthropic&#39;s counter-argument is that the higher intelligence leads to a higher ROI—you spend more per token, but you get the job done right the first time.&lt;/p&gt;
&lt;h3 id=&quot;2-the-data-policy&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#2-the-data-policy&quot;&gt;2. The Data Policy ⚠️&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;To defend against novel jailbreaks, Anthropic has introduced a &lt;strong&gt;mandatory 30-day data retention policy&lt;/strong&gt; for all traffic. This overrides previous &amp;quot;zero-retention&amp;quot; enterprise agreements. They claim this data is &lt;em&gt;not&lt;/em&gt; used for training, but strictly for security monitoring.&lt;/p&gt;
&lt;h2 id=&quot;final-verdict-practical-ai-take&quot; tabindex=&quot;-1&quot;&gt;&lt;a class=&quot;header-anchor&quot; href=&quot;https://drkpxl.com/claude-fable-5-the-safe-mythos-for-everyone/#final-verdict-practical-ai-take&quot;&gt;Final Verdict: Practical AI Take&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Fable 5 is a beast for anyone who needs a model that can actually &lt;em&gt;reason&lt;/em&gt; through a multi-step project rather than just predicting the next word. If you are building agents or handling complex technical debt, the 2x cost is likely negligible compared to the time saved.&lt;/p&gt;
&lt;p&gt;Just be mindful of the 30-day retention if you&#39;re handling extremely sensitive data, and keep an eye on your token usage—this model will eat through credits faster than Opus ever did.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;Want to see how Fable 5 integrates with Hermes and other automation tools? Stay tuned for the next guide.&lt;/em&gt;&lt;/p&gt;
</content>
  </entry>
</feed>