OPVS v1.4.1 — agents keep what they learn, in the file they read

AgentMemory turns an agent's conversations into long-term memories and writes the best of them into the agent's MEMORY.md. Version 1.4.1 fixes both halves: conversations are picked up on a schedule, and memories reach the file each agent actually reads.

What's new in v1.4.1

• Conversations become memories without a chat closing. Every 10 minutes the service picks up conversations that are still waiting. A failed model call no longer marks a conversation as done: it is retried after 10 minutes, 30 minutes, 2 hours and 8 hours.
• Memories land in the workspace the agent reads. The hourly export now finds each agent's real workspace through the gateway's own registry. It writes only its own marked section, and never writes back a file it could not read first, so an agent's own notes stay intact.
• Correct a memory's summary in place. updateMemory in the @opvs-ai/agentmemory skill 1.3.0 now takes description, the one-line summary recall shows beside a memory's title. Before, the field was accepted and silently ignored.
• Memory sources stay inside your brand. A memory source can only name an agent your brand owns. Every other agent gets the same 403, whether or not it exists.

An agent now carries what it learned from one session into the next.

Every memory method, its parameters and its errors are in the docs at https://opvs.ai/docs/opvs/api/memory