sukinai

4 ms·

1. 1.▲
   by sukinai 7mo ago

   I built Nemp Memory because I think there is an important distinction in AI memory: memory inside one AI tool is not the same as memory for your project. A lot of tools are adding their own memory now, which is useful. But if each tool has
2. 2.▲
   Show HN: Nemp Memory – local project memory that survives tool switching(nemp.dev)

   1 points by sukinai 7mo ago|1 comments
3. 3.▲
   by sukinai 7mo ago

   Really like this framing. Separating facts from ephemeral context seems like a very strong design choice, especially because each layer should probably have different health rules and validation logic. I have been thinking mostly about stal
4. 4.▲
   by sukinai 7mo ago

   This is super useful. I really like the idea of treating memory as an SLO surface rather than just a storage layer. Retrieval precision@k against a small gold set is a very strong suggestion. That feels like a much better early warning sign
5. 5.▲
   by sukinai 7mo ago

   AI memory is starting to behave less like a static notes file and more like a runtime dependency. If an agent depends on memory to retrieve prior decisions, project context, instructions, or compressed knowledge, then the quality of that me
6. 6.▲
   Show HN: I built a self-diagnostic health check for AI agent memory(github.com)

   1 points by sukinai 7mo ago|4 comments
7. 7.▲
   by sukinai 8mo ago

   OpenClaw is great at running multiple agents, but shared “project truth” still tends to live in chat scrollback: stack choices, auth rules, API conventions, and the “don’t break this” stuff that new agents keep re-asking. Nemp Memory makes
8. 8.▲
   Show HN: Nemp Memory for OpenClaw, shared memory for multi-agent workflows(github.com)

   1 points by sukinai 8mo ago|1 comments
9. 9.▲
   by sukinai 8mo ago

   Thank you so much Syed
10. 10.▲
    by sukinai 8mo ago

    Thank you AI Agents
11. 11.▲
    by sukinai 8mo ago

    Thank you
12. 12.▲
    by sukinai 8mo ago

    Yesterday Anthropic shipped agent teams with Opus 4.6. I had been building a memory plugin for Claude Code that stores project decisions as plain JSON on disk, and I wanted to see if it would work across parallel agents without any changes.
13. 13.▲
    Show HN: Claude Code agent teams with real time shared local memory(github.com)

    2 points by sukinai 8mo ago|6 comments
14. 14.▲
    by sukinai 8mo ago

    Will check it
15. 15.▲
    by sukinai 8mo ago

    I built Nemp Memory because I got tired of re-explaining my project to Claude Code every session. Auth strategy, API patterns, deployment setup, all gone after compaction or a new session. Nemp is persistent local memory for Claude Code. Ev
16. 16.▲
    Show HN: Nemp – Claude Code memory with zero cloud (just JSON on your machine)(github.com)

    1 points by sukinai 8mo ago|1 comments
17. 17.▲
    by sukinai 8mo ago

    Thanks for sharing, privacy-first + offline LLMs + P2P collab is a spicy combo (and ambitious to ship solo). A couple architecture questions: For the WebRTC + CRDT layer: how are you handling identity/auth (who’s allowed to join), and
18. 18.▲
    by sukinai 8mo ago

    Thanks for sharing this. Real-time governance at the moment of consumption is exactly the pain point—most teams only notice the “token surprise” when finance forwards the bill. Curious: how do you handle streaming responses and tool calls i
19. 19.▲
    by sukinai 8mo ago

    This hits the real problem: once agents execute code, “please don’t read ~/.ssh” is not a security control. Kernel-enforced isolation + tight allowlists is. The secrets workflow (keychain/secret service → env → zeroize) is especia