Question for the group: has anyone used AI to streamline managing project tasks like material ordering, POs, and tracking requested vs. received items? As a PM, I find it's becoming overwhelming. Currently, I track everything in Excel, which works, but it seems like there should be a more efficient approach. I even tried creating my own "Jarvis" to monitor it all, but it's still rough. I’m curious if anyone has found a solution—whether it's a custom tool, an existing product, or a workflow that just clicked.

What We Learned Building an AI That Remembers I spent an evening this week untangling a problem that sounds small and turned out to matter a great deal. We were building memory into the AI system that runs our agency, and I kept getting it wrong in the same way. The fix taught me something that reaches well beyond software, so it felt worth sharing. Here is the heart of it. When you ask something to remember, you are really asking for two different things, and they want opposite treatment. The first we call the learning log. It holds what you have decided and how you work right now. It is alive. You update it when something changes and you take things out when they are resolved. It is meant to be tidied, because its whole job is to reflect the present. The second we call the activity log. It holds what actually happened, and when. A piece of work delivered. A sign-off given. A decision made on a Tuesday. You only ever add to it, and you never rewrite it. Its value comes from staying untouched, because that is what makes it trustworthy later. So one is constantly revised and one is never revised. That single difference is the whole story. Why keeping them apart matters: The mistake we kept making was pouring both into one place. Do that and neither job gets done. If the daily record floods into the "how we work now" file, that file stops being a clear picture of the present. You end up wading through a diary to find the one rule you actually need. And if you keep your evolving decisions inside the daily record, you can never tidy them, because the record is supposed to stay frozen. Two honest jobs, pulling in opposite directions, sharing one drawer. The part that surprised us The harder question was not where to keep things. It was what is even worth writing down. Our first instinct was to log everything, every small step the system took. That turned out to be noise. The rule that actually worked was simple: only record what a person would genuinely mention in a monthly review. Something delivered. A decision reached. A problem raised or cleared. Everything else, the busywork in between, does not earn a permanent line. A memory that records too much is almost as useless as one that records nothing, because you can no longer find the moments that mattered.

I've been using Claude exclusively for a few months now. Started with openclaw, but that's a whole other story... I'm considering switching to antigravity. Gonna test it out tonight but wanted to see what you guys think about it as far as reliability and coding, etc Any direction is appreciated.