Dallas, TX
Joined April 2007
Anthropic shipped a full source map inside the Claude Code npm package. I read it. Here's how the memory system actually works at the source level. It's more thoughtful than most people assume. 🧵
1
1
2
78
Where it gets interesting: there's no provenance tracking. A memory doesn't know which conversation created it or what evidence supported it. Staleness is purely mtime-based. The system compensates with behavioral guardrails "the memory says X exists is not the same as X exists now" — but the gap is real. There's also no automated cleanup. Old memories persist until you manually delete them. And the 200-file scan cap means active projects could eventually hit ceilings. These aren't dealbreakers, but they're worth knowing if you're a power user relying heavily on memory. Practical tips from reading the source: → Keep MEMORY.md entries to one line, under 150 chars → Put detail in topic files, not the index → Write specific description: fields — it's your recall ranking function → Check ~/.claude/projects/*/memory/ to see what's accumulated
1
1
40
If you're interested in how AI memory systems work more broadly, including provenance, trust state, and cross-tool portability that's what I'm building at @statelessagent statelessagent.com
12
perfect timing, just shipped a little something i built with 4.5 this week. SAME - Stateless Agent Memory Engine statelessagent.com
Introducing Claude Opus 4.6. Our smartest model got an upgrade. Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta.
2
53
Sean retweeted
Introducing Claude Opus 4.6. Our smartest model got an upgrade. Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta.
1,658
4,627
2,897
38,677
10,625,915
Things are moving so fast. introducing a concept i've been working on - Stateless Agent Memory Engine, or SAME the problem: every ai session starts from scratch. you re-explain your project, paste in context, forget what decisions y'all made together. You spend 10 min setting back up and lose your focus. SAME fixes that. it indexes your markdown notes locally and automatically surfaces the relevant stuff when you start a session. decisions get logged. sessions hand off to each other. your agent actually remembers. how it works: → ollama embeds your notes on your machine → sqlite stores the vectors → your prompt gets matched to notes that matter → context shows up automatically no files leave your laptop. fully local. Context goes to your AI tool the same as pasting it yourself. works with claude code, cursor, windsurf — anything that speaks MCP. built this in a week with opus 4.5. made it for myself but maybe it helps you too. first thing i've shipped publicly. very nervous. feedback welcome. poke holes in it. <3 statelessagent.com
1
24
A tornado watch has been issued for parts of Arkansas, Oklahoma and Texas until 10 PM CST – at Texas, USA
30
380
92
673
294,133
I asked @openai's ChaptGPT to write a song about a rock in the style of #ZachBryan and frankly it slaps
1
2
280
I forced a bot to watch over 1,000 hours of the John Wick movies and then asked it to write a John Wick movie of its own. Here is the first page.
623
5,275
914
16,066
Ready Freddie? Retweet for your chance to win the Queen of all trips. The winner will get to see the London red carpet screening of @BoRhapMovie from #TMobileTuesdays. #contest

4,911
25,944
3,868
5,219
What a glorious haul we have for this week's #WinWednesday giveaway! Follow us and retweet for a chance to win a #SeaOfThieves journal, pencil, sticker set and pin badge! Get your entries in before 4PM GMT tomorrow. Good luck!
257
4,864
181
2,395