Deploy mem0 to vega and validate cross-agent memory sharing

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

nimmo/nixos-config#46

nimmo commented

2026-07-02 07:23:21 +01:00

Owner

Scope

Deploy the mem0 stack to vega and validate end-to-end memory sharing across agents.

Pre-deploy checklist

mem0-nix wrapper repo builds both packages successfully in CI
nix flake check passes with the new flake input + module
secrets/mem0.yaml created and encrypted with SOPS
Postgres + pgvector running on vega (local instance or existing)

Deploy steps

sudo nixos-rebuild test --flake .#vega with mem0 enabled
Verify mem0-server systemd service starts and Alembic migrations run
Verify dashboard accessible on Nebula IP
Run make bootstrap equivalent (create admin user + first API key)
Store generated API keys in SOPS

Post-deploy validation

Paseo agent on vega can omp_recall / omp_remember (or mem0 MCP equivalent)
Paseo agent on lyra reads memories written from vega
paseo-desktop on electra reads memories written from servers
opencode session can search/add memories
Backrest backup includes /srv/services/mem0
Service failure monitor posts to ntfy if mem0-server dies

Rollback

Standard NixOS generation rollback. Postgres data persists in /srv/services/mem0 — survives rollback but not a nixos-rebuild that removes the volume mount.

## Scope Deploy the mem0 stack to vega and validate end-to-end memory sharing across agents. ### Pre-deploy checklist - [ ] `mem0-nix` wrapper repo builds both packages successfully in CI - [ ] `nix flake check` passes with the new flake input + module - [ ] `secrets/mem0.yaml` created and encrypted with SOPS - [ ] Postgres + pgvector running on vega (local instance or existing) ### Deploy steps - [ ] `sudo nixos-rebuild test --flake .#vega` with mem0 enabled - [ ] Verify `mem0-server` systemd service starts and Alembic migrations run - [ ] Verify dashboard accessible on Nebula IP - [ ] Run `make bootstrap` equivalent (create admin user + first API key) - [ ] Store generated API keys in SOPS ### Post-deploy validation - [ ] Paseo agent on vega can `omp_recall` / `omp_remember` (or mem0 MCP equivalent) - [ ] Paseo agent on lyra reads memories written from vega - [ ] paseo-desktop on electra reads memories written from servers - [ ] opencode session can search/add memories - [ ] Backrest backup includes `/srv/services/mem0` - [ ] Service failure monitor posts to ntfy if mem0-server dies ### Rollback Standard NixOS generation rollback. Postgres data persists in `/srv/services/mem0` — survives rollback but not a `nixos-rebuild` that removes the volume mount.

nimmo added this to the Mem0 Memory Layer Integration milestone

nimmo added the

phase:deploy

service:mem0

host:vega

labels

nimmo closed this issue

2026-07-11 12:31:36 +01:00