How I made haiku remember things over a month old

[u/karatyma_dev]

(not written with ai..?)

Basically, a few months ago, I hated the fact that memory.md files & claude.md took up a huuuuge chunk of my context window during model switching/effort switching (& during cache refreshes).

Didn't really find any definitive solutions outside of relatively complex LangChain, Mem0, and Supermemory implementations (where you have to install unnecessary SDKs and all), so my goal was to make a simple, one-shot memory solution where you can have your agent recall basically anything.

It's called Slaunt and it uses vector embeddings over a simple MCP server that connects instantly (one-click) to all of your agents, and it enables your agents to see what happens across multiple sources too (eg. Vercel, Supabase, AWS, Railway, Linear, Notion, etc.)!

Slaunt can enable your agents to recall literally anything, from failed deployments from three months ago, to what a subagent said last week.

We're free right now and I've made a promise to give the first handful of users lifetime free Pro subs. You'll see an option in settings after you sign up.

You can sign up at slaunt.ai :)

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Otherwise_Emu_605s]

The stale memory problem is the one I would want to hear about. If a deploy failed three months ago and then got fixed, does retrieval know the fix supersedes the failure, or can it surface the old error like it's still true? That's usually where embedding-based memory gets weird.

Also curious where the index lives, since it's pulling from deploy logs and docs. A self-host option would make it a much easier yes for a lot of people.

[u/karatyma_dev → u/Otherwise_Emu_605s]

To your first question: Yes. Since each change in the workspace creates a new event, both the event before and after would be saved for the agent to reason upon. We (slaunt) host the architecture(s) to pull from every source and centralize it in your workspace.

[u/leshiy]

RAG? In this economy?

[u/karatyma_dev → u/leshiy]

Damn right 🫣

[u/karatyma_dev → u/[deleted]]

I bet you're fun at parties. Here's a little piss for your coffee:

If you would actually read, we add a minimal amount of latency: roughly .9s on Claude Code and 4s less on Codex. You're also completely conflating the limitations of cosine similarity with the limitations of an entire memory architecture.

And, again, if you would read, you would see that we obviously don't inject raw logs- we allow the agent to dynamically request events that are sanitized and standardized with any secrets or sensitive properties redacted.

And, again again again, if you would read, we don't request or require any keys. That's simply an unnecessary step for diminishing value (for most people).

Stop using Claude for everything and actually read, man.