Would you be open to supporting JSON-based configuration for pi-memory?
Right now, every setting uses an environment variable. This makes persistent configuration awkward and dependent on how Pi was launched. It is also harder to see and manage the active settings in one place.
One option would be a piMemory key in ~/.pi/agent/settings.json. A shorter memory key would be nice, but it might conflict with a future built-in Pi setting. Another option would be a dedicated file such as ~/.pi/agent/extensions/pi-memory.json.
Environment variables could remain supported as optional overrides, preserving the current behavior.
What do you think?
Would you be open to supporting JSON-based configuration for pi-memory?
Right now, every setting uses an environment variable. This makes persistent configuration awkward and dependent on how Pi was launched. It is also harder to see and manage the active settings in one place.
One option would be a
piMemorykey in~/.pi/agent/settings.json. A shortermemorykey would be nice, but it might conflict with a future built-in Pi setting. Another option would be a dedicated file such as~/.pi/agent/extensions/pi-memory.json.Environment variables could remain supported as optional overrides, preserving the current behavior.
What do you think?