{"repo":"taylorsatula/mira-OSS","free":true,"listed":false,"github":"https://github.com/taylorsatula/mira-OSS","clone":"git clone https://github.com/taylorsatula/mira-OSS.git","description":"This is the public release of MIRA OS. Discrete memories decay through momentum loss, tools auto-configure when dropped into tools/ folder, and the system prompt composes from modular trinkets. I would like to think I've made an elegant brain-in-box. You load it and send cURL requests - it talks back, learns, and uses tools. Contributions welcome.","language":"Python","stars":476,"topics":["ai-agents","ai-assistant","ai-memory","anthropic","chatbot","long-term-memory","memory-management","open-source","postgresql","python"],"license":"AGPL-3.0","category":"ai-agents","readme_excerpt":"I had the idea to build a recipe generator that could incorporate my cuisine preferences. 10,000 scope creeps later MIRA is a comprehensive best-effort approximation of a continuous digital entity. This is my TempleOS. Self-directed Mira accomplishes the end goal of continuity and recall through a blend of asynchronous conversation processing akin to REM sleep and active self-directed context window manipulation. There is one conversation thread forever. There is no functionality to \"start a new chat.\" This constraint forces facing the hard questions of how to build believable persistence within a framework (forward pass transformers) that is inherently ephemeral. Active conversation history stays live while it is relevant. Older material collapses into first-person memories. If an active conversation gets too large before it naturally collapses, MIRA compresses older messages into one rolling continuation brief while leaving the most recent turns untouched. First-Person Memory When a conversation segment collapses, Mira generates a first-person summary (\"I debugged the IndexError in process batch.py...\") rather than third-person (\"The assistant discussed debugging...\"). Early on I noticed third-person summaries created epistemic distance: Mira read them as logs about someone else, not memories of work It actually did. Absolute timestamps (\"On Jan 8\") replace relative time (\"Yesterday\") because relative time becomes a lie the moment the sun sets. When generating a new segment","default_branch":null,"files":null,"tree":[],"storefront":"/r/taylorsatula","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/taylorsatula/mira-OSS/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}