Skip to content

Cross-machine memory

Switch machines. Keep the project.

A development machine, a production server and a Telegram bot each saw a different part of the work. Alessandro gave all three a shared place to remember it.

Inside Alessandro’s fleet
  • DevelopmentCoding sessions and local capture
  • ProductionShared records and vector search
  • TelegramBot sessions and automation

All three workers forwarded events to the operator’s shared server.

Start where the work happens.

Each worker began with a local SQLite database. Alessandro used content hashes to identify duplicates as records travelled between machines. On May 12, his migration brought 22,116 unique observations and 311 sessions into Postgres with zero reported import errors.

Give every workstation the same history.

His customized server then accepted hook events from all three machines. The development environment could write a record; a bot on another machine could search the shared index. Postgres, Redis and Qdrant were infrastructure choices he made for this fleet.

Claude-Mem

Give your next session a head start.

We capture the decisions and fixes while you build. CMEM Pro puts that memory within reach of your connected tools.