•
> The model that underlies Claude Fable 5.2 and Claude Mythos 5.2 is a step forward in general capabilities. However, during the model’s training, we took steps to limit advances in the specific research capabilities that could most directly accelerate AI development. Thus, in relevant areas, including accelerator kernel optimization and improving large language model architectures, Fable 5.2 and Claude Mythos 5.2 perform at about the level of Opus 5.5. Importantly, we ensured that the training changes did not affect related capabilities like agentic coding, hardware development, and traditional AI or machine learning research (including interpretability research). We do not alter these capabilities as the model is being served to users (that is, at inference time). As described in Section 1.5 of the System Card and similarly to previous models, Fable 5.2 and Claude Mythos 5.2 also include transparent fallbacks to Opus 5 for a small set of topics in this domain, including kernel development on certain nonstandard accelerators. ----- > Be it enacted by the Senate and House of Representatives of the United States of America in Congress assembled, > Sec. 1. Every contract, combination in the form of trust or other- wise, or conspiracy, in restraint of trade or commerce among the several States, or with foreign nations, is hereby declared to be illegal. Every person who shall make any such contract or engage in any such combination or conspiracy, shall be deemed guilty of a misdemeanor, and, on conviction thereof, shall be punished by fine not exceeding five thousand dollars, or by imprisonment not exceeding one year, or by both said punishments, at the discretion of the court. > Sec. 2. Every person who shall monopolize, or attempt to monopolize, or combine or conspire with any other person or persons, to monopolize any part of the trade or commerce among the several States, or with foreign nations, shall be deemed guilty of a misdemeanor, and, on conviction thereof; shall be punished by fine not exceeding five thousand dollars, or by imprisonment not exceeding one year, or by both said punishments, in the discretion of the court.
••••••••••••••••••••••••••••••••••••••••••••••••••••
It solves for the same thing a "train of thought" (internal vocalization) solves for in the human brain: there's a lot of stuff you "know" as episodic memories of words you've heard/read, but haven't yet internalized via practice into reflex reactions. It's a lot faster and cheaper to acquire a memory of some words, than it is to acquire an entire new skill, so you end up picking up far more memories-of-words than concrete skills from a given training corpus. Reasoning (i.e. bubbling those remembered words up into your mental context, and then using a special "trigger effectively arbitrary synaptic activations dependent on the content of the attention-masked context and an ongoing state" bridging reflex on them, a.k.a. "system-2 thinking") is how you leverage memories-of-words into useful behavior. Rather than executing native skills embedded into your synaptic weights, you're running a single very fancy native skill that acts as an interpreter for word-memory data, slowly and strenuously turning words you're holding in mind into more words (synthesis), or into associations to other memories (word-memories or otherwise), or into actions/outputs, etc. (An especially useful "trick" of this system is planning , i.e. chaining the interpreter through "mere words" that conjure more "mere words" to mind until you end up at words that form a declaration of what you're about to do. You can then rely on a special part of the bridging reflex, namely the "instruction-following" reflex, to react in a way where your actions are constrained by the plan you've generated.)
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
100% agree. Home Assistant is the brain of my smart house and my rule has been, for over a decade now, that all smart devices should fail back to being dumb and anyone in my house should be able to use the house without an instruction manual. In practice this looks like Z-wave smart switches everywhere for lights so that you can control the light via automation, app, the switch on the wall, or Alexa. They all feed into the same system. LLMs have made this even easier and removed some of the annoying fiddling I used to do in the past. Now I can open up Claude Code and tell it to build a new automation and it's done in minutes. Yesterday I realized I left the floodlight on in the backyard by accident, not problem "Claude, create an automation in home assistant to turn off backyard light 5 minutes after I turn it on", done. Could I have created that automation? Yes, I've written countless of them in that past but now I can speak it into existence and, almost more importantly, tweak it with barely any effort at all. If tomorrow I buy a motion sensor I can just ask the LLM to incorporate that, if I want the lights to stay on if X other device is turned on, it's a prompt away. In the past I would spend a good bit of time writing an automation but when it broke down or my needs changed it was enough friction that I would just give up and turn off the automation rather than take the time to debug and change it. I setup all the motion-activated lights in my house when I first moved in and over the course of a few weeks I tweaked each one as needed with just a short prompt here or there, it felt like living in the future.
••••
I've recently come up with what I think is an even better solution. If someone's already done it, I have no idea. I just went ahead and implemented it because I thought it'd be interesting. The concept is that, instead of assuming that IP and MAC addresses are at all reliable, to "fingerprint" devices on the LAN based on things such as SSH public keys, TLS SPKI fingerprints, UPnP device UUIDs, mDNS, common TCP port profiles, and IEEE OUI manufacturer in order to form mostly-stable identities. The IP and full MAC are only fallen back to when there's absolutely no other data to work off of. My software uses a daemon that scans the network in order find devices and update existing device identities if IPs change. It serves hostnames for these devices on the `.home.arpa` TLD and creates synthetic IPv6 addresses for each device in case one would rather use their own DNS server or hosts file. I recently "finished" this project, and it's kind of awesome because I was able to swap to a new router and everything just kept working as-is without having to think about it. Of course mDNS solves a lot of these problems already, but not every device has mDNS. What's really cool is I recently realized that this is also very useful for accessing your local network with a VPN like Wireguard. Even though I only planned on this being something you run on individual clients, I put it on my OpenWrt router and configured it with dnsmasq so that, when I connect to my network with Netbird, all of my local hostnames just work on my phone by virtue of connecting to the network and using its DNS server. That said, my project doesn't require router admin access at all. It can even run as rootless if TUN access (for synthetic addresses) is turned off. Maybe I'll release it publicly at some point, but if anyone wants to steal this idea and do their own implementation, I am not territorial over it. It's made getting my LAN devices working together a joy.
 Top