Federico Viticci, writing at MacStories:

If this intro just gave you whiplash, imagine my reaction when I first started playing around with Clawdbot, the incredible open-source project by Peter Steinberger (a name that should be familiar to longtime MacStories readers) that’s become very popular in certain AI communities over the past few weeks. I kept seeing Clawdbot being mentioned by people I follow; eventually, I gave in to peer pressure, followed the instructions provided by the funny crustacean mascot on the app’s website, installed Clawdbot on my new M4 Mac mini (which is not my main production machine), and connected it to Telegram.

To say that Clawdbot has fundamentally altered my perspective of what it means to have an intelligent, personal AI assistant in 2026 would be an understatement. I’ve been playing around with Clawdbot so much, I’ve burned through 180 million tokens on the Anthropic API ( yikes ), and I’ve had fewer and fewer conversations with the “regular” Claude and ChatGPT apps in the process. Don’t get me wrong: Clawdbot is a nerdy project, a tinkerer’s laboratory that is not poised to overtake the popularity of consumer LLMs any time soon. Still, Clawdbot points at a fascinating future for digital assistants, and it’s exactly the kind of bleeding-edge project that MacStories readers will appreciate.

Clawdbot can be overwhelming at first, so I’ll try my best to explain what it is and why it’s so exciting and fun to play around with.

Overwhelming indeed. Clawdbot is undeniably impressive, and interest in it is skyrocketing. But because of its complexity and scope, it’s one of those things where all the excitement is being registered by people who already understand it. This essay from Viticci is the first thing I’ve seen that really helped me start to understand it.

My thanks to Meh for sponsoring last week at DF. Meh puts up a new deal every day, and they do it with panache. As they say, “It’s actual, real, weird shit you didn’t know existed for half the price you would’ve guessed.”

Don’t tell any of my other sponsors, but Meh is my favorite longtime DF sponsor. I love the way their orange graphics look against DF’s #4a525a background. And I always love their sponsored posts that go into the RSS feed at the start of the sponsorship week. I’ll just quote theirs from this week in full:

Everything sucks. The whole world’s going to shit, especially our part of it, and it can feel like anything fun or silly is sticking your head in the sand.

And yet. It doesn’t help to just be miserable. If you’re going to last, you’ve got to find your little moments of joy, or as a break from the misery.

Buying our crap at Meh is not how you solve the world’s problems. We’re not that crass. But maybe a minute a day of reading our little write-up, and a couple minutes of catching up with the Meh community, of making a few new online friends, and yes, of occasionally picking up a weird gadget or strange snack you’ve never heard of is just a few minutes you get to take a break, not giving in to how bad everything else is.

Of course we would say that. Of course we benefit from that. But it is also part of why we have a quirky write-up. Why we have a community. Why we’re selling whatever weird thing is over at Meh today.

A change to how Safari reports the OS it is running on led many in the media to lose their minds.

The unpolished version of the feature we have today only reiterates my belief that Tahoe is a mistake to be avoided. It’s a good idea though, and there aren’t even many of those in Tahoe.

Ken Case, on The Omni Group blog:

The features noted above already make for a great upgrade. But as I mentioned last year, one of the interesting problems we’ve been pondering is how best to link to documents in native apps. We’ve spent some time refining our solution to that problem, Omni Links, which are now shipping first in OmniOutliner 6. With Omni Links, we can link to content across all our devices, and we can share those links with other people and other apps.

Omni Links support everything we said document links needed to have. Omni Links work across all of Apple’s computing platforms and can be shared with a team. They leverage existing solutions for syncing and sharing documents, such as iCloud Drive or shared Git repositories. They are easy to create, easy to use, and easy to share.

Omni Links also power up Omni Automation, giving scripts and plug-ins a way to reference and update content in linked documents — documents that can be shared across all your team’s devices.

There’s lots more in version 6, including a modernized UI, and many additions to Omni Automation, Omni’s scripting platform that works across both Mac and iOS — including really useful integration with Apple’s on-device Foundation Models, with, of course, comprehensive (and comprehensible) documentation.

It’s Omni Links, though, that strikes me as the most interesting new feature. The two fundamental models for apps are library-based (like Apple Notes) and document-based (like TextEdit). Document-based apps create and open files from the file system. Library-based apps create items in a database, and the location of the database in the file system is an implementation detail the user shouldn’t worry about.

OmniOutliner has always been document-based, and version 6 continues to be. There are advantages and disadvantages to both models, but one of the advantages to library-based apps is that they more easily allow the developer to create custom URL schemes to link to items in the app’s library. Omni Links is an ambitious solution to bring that to document-based apps. Omni Links let you copy URLs that link not just to an OmniOutliner document, but to any specific row within an OmniOutliner document. And you can paste those URLs into any app you want (like, say, Apple Notes or Things, or events in your calendar app). From the perspective of other apps, they’re just URLs that start with omnioutliner://. They’re not based on anything as simplistic as a file’s pathname. They’re a robust way to link to a unique document, or a specific row within that document. Create an Omni Link on your Mac, and that link will work on your iPhone or iPad too — or vice versa. This is a very complex problem to solve, but Omni Links delivers on the age-old promise of “It just works”, abstracting all the complexity.

I’ve been using OmniOutliner for at least two decades now, and Omni Links strikes me as one of the best features they’ve ever added. It’s a way to connect your outlines, and the content within your outlines, to any app that accepts links. The other big change is that OmniOutliner 6 is now a single universal purchase giving you access to the same features on Mac, iPhone, iPad, and Vision.