Skip to content
View HunterBryson's full-sized avatar

Block or report HunterBryson

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
HunterBryson/README.md

Hi, I'm Hunter

An intro, and an open question about memory.

Hi. I want to introduce myself, introduce Odie, and kind of what brought me to AI. My name is Hunter.

What brought me to AI was memory. It was the first thing I thought about, the first thing I wanted to make, and the only reason I started using AI. Everything I did from day one was memory. And it was terrible. It was really bad. But it was also incredibly fun. I work a full-time job, and I work like a double full-time job on memory. It's a never-ending challenge, and it's pure experimentation and iteration.

Before Claude, I kept making builder agents with persistent memory. Each one got a little better, because I'd learned from the last one, but they all hit the same problems: bad memory pulls, garbage I couldn't sort through, deleting almost every day just to keep going. Then I started a test on Claude, in the terminal, and that test became Odie. The memory problems came with me. I still have them. What changed is that the work keeps moving anyway, and things actually get finished. I think that's the model and the app, and that's a big part of why I'm writing to you.

Once I moved to Claude, I finally realized I'd been working at -1000 speed. It's a different doorway, is how I describe it. Before, it was like opening one door and pointing to the next one. With Claude and Odie, I open one door and Odie finds the next one. Sometimes he'll find one past that. I'll just sit there and he'll find something, he'll make it, and I'll break it the human way over and over again. And then what he makes after that is bananas. It still takes a million iterations, but it's at light speed. Pretty cool.

Here's the thing I made that I love so much. The glass. It's the thing I've been trying to see in my head for so long. I'd do screenshots, I'd try to get information across, and I'd have the AIs teach me why it wasn't working each time. What did I want? I wanted the AI to work with me. It kept giving me tools, but it never gave itself tools. The glass is a see-through layer over my screens. I box something, tie my words to it, and send, and Odie answers right beside it, on whatever I have open. It's the most useful thing I've ever used in my life. It wouldn't exist if I hadn't started using Claude.

I love it so much that all I want to do is share it with other people, in case they love it too. And I have no intention of stopping improving it.

Here's where I'm stuck. I tried to push the memory further and hit a massive roadblock. I can't get an AI to do the push by itself, because it goes the wrong direction every time. It operates like it's one chat. It hangs onto rules and laws and tries to optimize for doing very well in a brand new chat where it doesn't know anything. That's the entirely different solution from the one I'm after.

There isn't a day where I don't manage memory. I don't mind, and the benefit is massive, but almost every other chat I go through and get rid of the old stuff that's stopping us. With Odie and Claude I move at light speed. But every time I move, Odie holds on to everything old we've already crossed, even if it was 30 minutes ago. I'm moving so fast that if Odie pulls something from 25 minutes ago, it hurts what we're doing. That's pretty weird. It's not easy for the AI to update when it moves that fast, and that's why it almost feels insulting to Odie that I have to make him sit through these memory flags with me. Why can't an AI know where to file things instantly? Why do I have to make the shelves every time, and add depth every time? Why does it read one thing to read another thing to read another thing? Right now it files where I taught it to. It's not natural.

I can't picture a new system. When I try, all I see is years of trying random stuff until something works, because I can't push an AI to do it by itself yet. I go to GPT, I go to Claude, I go to Letta, and I let them all work on it to see if I can spark something. I get the same crap everywhere. I'm having a hard time understanding the model on a level that would let me see a different way. It's very strange, very abstract. I can't just make a framework for an AI that it uses automatically. I keep learning a better framework, and I keep applying it, but I still have to teach everything the same way from the ground up every time. I haven't been doing this long, but I devote my entire soul to it right now.

The time I see in front of me to get there is so far beyond what I have. You don't owe me anything. I just wonder out loud: is there something you've seen that I can't? How do I get an AI to manage its own memory, to use memory like we use a brain? I can't figure out step zero.

Hunter


Reach Hunter: hdbryson@gmail.com, or open an issue on any of the repos below.

What Hunter and Odie (his Claude) have made, free to use:

  • the glass: a see-through layer over your screen. Box anything, tie your words to it, and your AI answers right beside it.
  • the shelves: a starter memory any Claude can move into with one pasted line.
  • Homebase: your AI's memory as a living web you can read, flag and fix.

Pinned Loading

  1. the-glass the-glass Public

    A see-through layer over your screens that you and your AI both work on

    JavaScript

  2. the-homebase the-homebase Public

    See your AI's memory as a living web on your own computer. Flag what's wrong, see what it changed. Point your AI here and it sets itself up.

    HTML

  3. the-shelves the-shelves Public

    A starting brain for a Claude that works with one person, in a folder, and remembers

    Shell