Hacker News new | ask | show | jobs
by comchangs 76 days ago
The persistent memory at ~/.nanopm/memory/ is clever. Having context survive across sessions is what makes this actually usable vs a one-shot prompt.

We did something similar with deployment presets in our CLI — saving frequently used server/module combinations so you don't re-specify them every time. The "memory layer" pattern seems to be emerging across all dev tooling.

1 comments

Thanks, agree. Without persistent context, users end up rebuilding state every time. Feels like memory is becoming a core abstraction (like env vars), not just an add-on.