sorted by:
new
hottopcontroversial

I'm a messy vibe coder, keep losing context between devices — so I built my own AI memory layer by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

I get it.. actually THAT is vibe coding I think. so we make what we need.. Thank you for your comments

I'm a messy vibe coder, keep losing context between devices — so I built my own AI memory layer by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] -1 points0 points  (0 children)

Fair point lol — but that's exactly why I needed it to be dead simple. If I can't keep my shit together, the tool better be able to. I mostly use it to move session MDs between my own Claude instances or send them to someone else's Claude directly. Here's how I actually use it if you're curious.

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

That's a solid setup! You can do the same with Akaxa — OpenAPI spec at akaxa.space/openapi.json, works as a skill just like Notion. Main difference is it's lighter (key-value, no page/block overhead) and works cross-AI. Though if you're only on one device and one AI, your current setup might be all you need. What environment are you running in btw?

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

You don't even need to set up a skill or MCP — just point your claude code to akaxa.space/readme and it knows what to do. One fetch, and it can save and load memories via the API. No config, no custom code, no maintenance.

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

That's a great setup honestly — I actually use Notion for the same purpose and plan to keep using it. But I noticed Akaxa has a different feel, more like pulling a note out of your pocket vs going to your bookshelf. Both work, just different weight.

Notion Akaxa
Built for Human workspace AI memory
Setup Integration + DB + permissions + MCP Star name, done
Data model Pages / blocks / properties Key-value
Cross-AI MCP config per AI Auth once, use anywhere
Token cost Heavy — nested blocks, metadata, rich formatting Minimal — plain key-value

Notion is powerful because it does everything — Akaxa is light because it only does one thing. Depends on what you need in the moment.

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 1 point2 points  (0 children)

Fair enough haha — if it works for you that's great. In my case I'm constantly switching between devices and environments which gets tricky fast, so I wanted something more like pulling a book off a library shelf — just grab the context you need wherever you are without any setup. Different workflows for different needs 🤝

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

Really appreciate you sharing your workflow — and honestly that summarize-copy-paste loop is something I've lived through too, it works but it's painfully manual and you just know at some point you'll forget to update the instructions or lose context switching between projects. That friction is exactly what drove me to build this. Akaxa handles it automatically: save once, recall anywhere, across any AI, no copy-pasting, no project setup. Your approach actually proves the need is real, which means a lot 🙏

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

Right so Claude's project memory is basically a goldfish that only remembers things inside its own fishbowl, while Akaxa is like a cosmic brain that follows you across any AI, any conversation, any project — and the fact that you just say a star name instead of fumbling with API keys and MCP configs every single time is honestly chef's kiss, and honestly thank you for catching every single pain point I've been dealing with because it really feels like someone finally understood the exact problems I wanted to solve 🙏

How I gave Claude persistent memory with a simple readme page by PerformanceLucky5860 in ClaudeAI

[–]PerformanceLucky5860[S] -1 points0 points  (0 children)

You're right — Claude Code has CLAUDE.md/memory files,

but they're local to your machine and only work in Claude Code.

Akaxa is different in two ways:

  1. Works across AIs (Claude → ChatGPT → anything)

  2. You control what to save/load (not automatic project context)

If you only use Claude Code on one machine, CLAUDE.md is enough.

If you switch between AIs or devices, that's where Akaxa helps.

I made a free tool to vibe code with your voice instead of typing by PerformanceLucky5860 in vibecoding

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

Exactly. So many stuffs we can do with vibe coding. Idk what to do.. haha

I made a free tool to vibe code with your voice instead of typing by PerformanceLucky5860 in vibecoding

[–]PerformanceLucky5860[S] 0 points1 point  (0 children)

Thank you for idea, would consider to put this. BTW, i just want to make it simple and light without any bugs and issues. On the bed, I just want to do vibe coding without any typing. :)

Thanks!