akitaonrails/ai-memory

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on August 17th, 2026
Created on May 21st, 2026
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 250
Total Stargazers: 2,989 (+1)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.7 hours
Mean response time: 11.7 hours
90th percentile: 24.2 hours
Tracked items: 133

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 21% of issues opened in the past year have been closed. Three people close 97% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 9
Closed in 7 days: 9
Avg open age: 3 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 9
Closed in 7 days: 7
Comments in 7 days: 6
Events in 7 days: 18

Top labels

  • enhancement (30)
  • bug (21)

Detailed Description

ai-memory is a persistent memory system for AI coding agents that enables continuity across different agent vendors and CLI sessions.

The tool solves the problem of context loss when switching between different AI coding agents or interrupting and resuming work. Rather than re-explaining project architecture, failed approaches, and open questions each time, ai-memory stores agent state and reasoning in a structured format that persists across sessions. This allows developers to pause work with one agent vendor and seamlessly continue with another, or resume the same agent later without losing accumulated context.

Developers should adopt this tool if they work with multiple AI coding agents or frequently interrupt and resume coding tasks. It suits projects where maintaining continuity across agent handoffs is valuable, particularly in exploratory development or when comparing different agent capabilities on the same codebase. The README positions it specifically for scenarios like quitting Claude Code mid-task and continuing with OpenAI Codex in the same directory without repeating explanations.

The project responds to issues and pull requests within a day. Development activity centers on enhancements and bug fixes. The project is growing steadily.