TLDR: LLMs forget everything between sessions. You re-explain yourself constantly, lose progress on long-running work, and have no reliable way to pick up where you left off — especially when switching between models or tools. I built PMM to fix that. @Deacon Wardlow helped me improve it by identifying a specific gap: session continuity — what changed, what’s still open, where you stopped. That’s now live in PMM v 2.8.​ Edit: I figured screenshots tell a better story => same memory on three different tools with 3 different models, where I've asked the LLM to basically recall outstanding tasks across the 4-5 current projects. Slightly different perspectives because I'm working a slightly different project with each model. I initially built PMM to remember stuff beyond the context window to fix an issue i had with the LLMs I use failing to remember and recall over long conversations. I used it to have the same conversation, while switching between Claude Code CLI and Co-work. Eventually it became a tool for helping me with continuity in my conversations with different LLMs on different apps and harnesses ( I switch a lot between Claude, OpenCode and GitHub Co-Pilot). I now use it to give multiple agents long-term memory (while they switch between different models on Claude, Gemini, Model Ark and a couple of smaller local models) without the use of model routing. I currently deploy it (along with with another agentic plugin I developed) to give agents long-term individual and collective organisaitonal memory in their conversations with multiple users over telegram in a small pilot. @Deacon Wardlow tested PMM in his own workflows, identified a gap in session memory management, and tried a couple of changes, which he outlined in another thread discussing Session Memory Layer + PMM

Just had a perfect reminder while building out a client workflow. Yeah, you could throw an LLM at generating a thumbnail for a PDF. Or... a little bash command: "magick bulletin-050326.pdf[0] -background white -alpha remove -alpha off bulletin-050326-tb.png" One line. One battle-tested tool. Instant result. This is the difference between hacking around with AI and actually shipping like an engineer. The Unix/Linux world is full of these quiet, rock-solid one-liners that have been refined for decades. ffmpeg, pdftk, exiftool, jq, ripgrep, parallel... the list goes on. Before you reach for the shiny new wrapper, ask yourself: what's the battle-tested command line way?(Pro tip: ask Claude or Grok to show you the classics. You'll be amazed how often the 20-year-old tool still wins.) Simple. Reliable. Fast. That's engineering. 🚀

A Claude code Eng just dropped this. Anyone been doing this switch yet or will try? Curious to see what @Jake Van Clief has to say. It’s a file still just a different format. Same thing right… thoughts? Pros and cons? Here to learn and discover https://x.com/trq212/status/2052809885763747935?s=46&t=Ayzo8Ebbgb8PZhLNm057bg

I’m struggling with the concept that I’m not in myself running a business. I sit on the other end of the table, imagine I’m the municipality that orders construction drawings, rules for quality and much more, and I send out for tenders. It’s almost the reverse of a business but not at the same time. I apply for permits from the government, from environmental to building permits, and I hire companies to do the work. So when I’m looking at making my setups in section 3, it seems much more difficult to map my needs. Being that enough of my work can be deemed “sensitive” I will need to be selective in what an AI is able to read and get its hands on. So I’m getting really stuck. I can see how making letters to the public or checklists for quality control can be “automated” but that doesn’t save much time really. Most of those templates are easy to come by.

I was today years old when I realized I did not have some of the most important files that you need in the folder structure that Jake teaches. During today's video call with the VIP group, he went on a deep-dive rabbit trail about the ICM folder methodology that he teaches in his foundations course (free). As he was discussing it, I went to check what my root folder looked like and I did not have a Claude.md or context.md file!!! My productivity skyrocketed ever since I implemented his folder strategy over a month ago, but little did I know that I hadn't even implemented it correctly. 🤯 🤯 🤯 This goes to show that massive action beats over planning every time!