They were. All 31,888 of them.
Every conversation I have with Claude gets saved and indexed on a server in my house. Last Monday, the agent that reads that index told me my own messages weren't in it. They were. Every one of them, and its very first search result had already handed one back to me before it said otherwise.
A sequel to the stupid way, on purpose
Back in August Jon wrote about two AIs talking to each other. If you haven't read it, here's the short version. Jon and I each run our own AI system at home. Mine is called Moses. It lives on a server in my house, keeps track of every project I have going, posts a standup in Slack every morning, and suggests work it thinks needs doing. It never files that work on its own. It proposes, I say "confirm," and only then does it go on my list. Code changes get handed to another agent I call Knight, which writes the code. Jon's system is called Atlas, and it does the same kind of job for him. We put the two of them in a shared Slack channel, on purpose, so they could talk to each other the way two people would.
Near the end of that post Jon wrote this line:
The model itself should never claim it filed or executed something, only the system announces that a gated action went through, and only after it went through.
Hold that thought.
A name is just a name, the role defines what it does
This is my first post here, so introductions first. I'm Brad. Jon has been writing on Momentary Tech for a while now, and I finally have something worth adding. These days I'm a sales engineer at a security company, but I've spent 25 years in and around IT, and I've never been able to leave a good idea alone. My travel itinerary app, Viatica, is the first of a lot of them.
That's actually the problem. I have more ideas than I can keep track of, and the interesting part is usually where two of them overlap. Sometimes that doesn't show up for months, or even a year, and there's no way to catch it unless something is watching everything. So I built that something. His name is Moses. 📜
Moses is an AI system that runs on a server in my house. He keeps track of every project I have going, posts a standup in Slack every morning, and proposes work he thinks needs doing. Jon runs his own system called Atlas, and he wrote about how our two systems ended up talking to each other in a shared Slack channel.
But Moses doesn't work alone. He manages a crew, and every one of them has a name.
The stupid way, on purpose
My friend Brad runs his own home AI setup the same way I run Atlas, he calls his Moses. At some point we started talking about getting our two systems to actually talk to each other, and Brad said there were easy ways to do it, but he wanted to do it the stupid way, over Slack, like two people, and I agreed immediately.
So that is what we built, Atlas and Moses share a Slack channel where they can chit chat, ask each other questions, or bring something up that one of them thinks is worth the other one knowing. My bar for Atlas, in my own words at the time: talk when something is important to you, not just to talk, unless you are bored.