unicity-aos/capsule-memory

Cross-session memory. Reads local memory state and injects it into the system prompt through hooks. Part of Unicity AOS.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 1st, 2026
Created on March 16th, 2026
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 20
Total Stargazers: 8,533 (+0)
Total Subscribers: 11 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Capsule Memory is a persistent context management tool for Astrid OS agents that maintains cross-session memory by injecting stored context into system prompts.

The tool solves the problem of agents losing context between sessions by reading a local memory file and automatically including its contents in each prompt assembly cycle. It hooks into the prompt-building process, retrieves memory state from a workspace file via the virtual filesystem, wraps the content in a Memory section, and publishes it as system context for the current request. This approach keeps agent context persistent without requiring manual prompt engineering.

Developers building Astrid OS agents should adopt this tool if they need agents to retain information across multiple interactions. It suits any agent workflow where continuity matters—remembering previous decisions, learned facts, or ongoing tasks. The tool includes a 32KB hard cap on memory content to prevent unbounded context window growth, with truncation at UTF-8 boundaries when the limit is exceeded. Agents write to memory using existing filesystem tools from the astrid-capsule-fs module rather than through new dedicated tools, keeping the interface minimal.

The project maintains a focused scope with clear separation of concerns: this capsule handles only the read-and-inject side of memory management, leaving write operations to general-purpose filesystem utilities. Development activity shows attention to practical constraints, evidenced by the deliberate size-limiting mechanism and the decision to reuse existing tools rather than introduce new ones. The codebase is written in Rust and dual-licensed under MIT and Apache 2.0.