Skip to content

Roadmap

ai-memory-hub has completed its core local-first memory-service foundation. The roadmap now focuses on making that foundation easier to release, safer to operate, simpler to adopt from agent clients, and more useful as a memory product without weakening immutable history, authorization, provenance, or provider-neutral behavior.

GitHub owns roadmap scheduling and implementation detail:

Milestones answer when a reviewed set of work is targeted. Epics describe the larger outcome and its compatibility boundaries. Child issues should contain the PR-sized implementation work.

Current Direction

Stabilize and release

Complete repository governance, release rehearsal, security-boundary hardening, and the remaining verified import compatibility work. This is the shortest path from the implemented service to a repeatable, supportable release.

Improve provenance and adoption

Preserve exact agent/model provenance, package the existing MCP surface for Codex, and make setup and failure recovery clear across supported clients.

Build the memory product

Add a user-facing workspace and supported SDKs, then expand cited and rebuildable intelligence over immutable source memories. Lifecycle controls must remain explicit, audited, and permission-aware.

Expand privacy and storage deliberately

Add opt-in application encryption and graph/provider capabilities only with migration, recovery, isolation, quality, and operational evidence.

Roadmap Constraints

Every milestone and epic must preserve:

  • local-first operation and explicit opt-in for hosted or sync behavior;
  • immutable source-memory evidence and cited, rebuildable derived records;
  • owner, project, auth-scope, quarantine, and audit boundaries;
  • stable HTTP/MCP contracts or an explicit compatibility plan;
  • provider-neutral behavior, bounded fallback, and secret-safe diagnostics;
  • measurable quality, latency, storage, and model-cost guardrails.

See Project status for the evidence-based classification of what is done, partial, or not started. See Documentation and planning for the repository planning policy.