4 Repos
Systems that use version control to manage and track changes to agent memory filesystems.
Distinct from Agent Versioning: Distinct from Agent Versioning: focuses on the versioning of the memory data itself rather than the agent deployment version.
Explore 4 awesome GitHub repositories matching development tools & productivity · Versioned Memory Repositories. Refine with filters or upvote what's useful.
Letta is a framework for building, deploying, and managing autonomous AI agents that maintain persistent state across long-term interactions. It provides a comprehensive suite of primitives for defining agents with configurable personas, modular memory blocks, and tool-use capabilities, enabling them to retain user preferences and conversation history over extended sessions. The platform distinguishes itself through its advanced memory management and orchestration capabilities. It allows agents to autonomously update their own memory, perform retrieval-augmented generation, and coordinate com
Integrates git-backed filesystems to provide version control for persistent agent memory data.
DLSS Swapper is a desktop tool that manages and replaces upscaling DLLs in game directories, supporting DLSS, FSR, and XeSS technologies. It identifies DLL versions by computing file hashes and matching them against a known database, then swaps the files directly in the game folder without modifying executables or memory. The tool automatically detects installed games across Steam, GOG, Epic Games, Ubisoft Connect, Xbox App, and Battle.net, and also supports manual addition of games by specifying the executable path. It maintains a local repository of multiple upscaling DLL versions, allowing
Downloads and stores multiple versions of upscaling DLLs in a local cache for per-game selection.
DiskLruCache is a disk-backed key-value cache library for Android and Java environments that stores data on the filesystem within a configurable byte limit. It uses a least-recently-used (LRU) eviction policy to automatically remove old entries when the cache exceeds its allocated size, and maintains a journal file to reconstruct its in-memory state after a process restart. The cache provides atomic write operations that first write new data to a temporary file before atomically renaming it, preventing partial or corrupted reads during concurrent access. It returns frozen snapshots of cache e
Requires monotonically increasing version numbers per entry to detect stale or concurrent modifications.
Maintains a local cache of patch versions to allow downgrading or upgrading specific UI components.