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.
There's not really any congruent way to have an editor and a separate tool anymore. At least not in a way that makes sense, so for the moment im fine with them being in one place, thanks for posting this. this was a good deep dive for one of my projects.
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.
There's not really any congruent way to have an editor and a separate tool anymore. At least not in a way that makes sense, so for the moment im fine with them being in one place, thanks for posting this. this was a good deep dive for one of my projects.
[dead]
[dead]