Changelog

All notable changes to Memoria are documented here.

This project adheres to Semantic Versioning. The format is based on Keep a Changelog.

[Unreleased]

Changes that are in development but not yet released.

Planned

• Multi-file analysis in a single call
• Custom output formatters
• Integration with more AI tools

[1.0.0] - Initial Release

The first stable release of Memoria.

Added

• analyze_file tool — Core file analysis with git forensics
  • Volatility Engine: Panic keyword detection with time-decay scoring
  • Entanglement Engine: Co-change analysis with configurable threshold
  • Sentinel Engine: Stale dependency detection
  • Static Import Engine: Import relationship tracking
  • Evidence extraction: Actual code diffs in analysis output
• ask_history tool — Git history search for understanding code context
• CLI commands
  • memoria init — Auto-setup for AI tools
  • memoria analyze — Standalone file analysis
  • memoria serve — Start MCP server
• Configuration via .memoria.json
  • Customizable thresholds (coupling, drift, analysis window)
  • Ignore patterns with glob syntax
  • Custom panic keywords with weights
  • Risk weight configuration
• Auto-pilot mode — Automatic analysis rules for AI tools
  • Cursor rules (.cursor/rules/memoria.mdc)
  • Claude Code rules (.claude/memoria.md)
  • Windsurf rules (.windsurfrules)
  • Cline rules (.clinerules)
• Performance optimizations
  • LRU cache with 5-minute TTL
  • Smart filtering of noise (node_modules, build artifacts, etc.)
  • <100ms analysis time
  • ~600 tokens per analysis average
• Platform support
  • macOS
  • Linux
  • Windows

AI Tool Support

• Claude Desktop
• Cursor
• Windsurf
• Continue (VS Code)
• Cline

Version Format

Memoria follows Semantic Versioning (SemVer):

MAJOR.MINOR.PATCH

MAJOR - Breaking changes (incompatible API changes)
MINOR - New features (backward compatible)
PATCH - Bug fixes (backward compatible)

What Constitutes a Breaking Change?

• Changes to tool input/output schemas
• Removal of configuration options
• Changes to default behavior that could affect existing workflows
• Minimum Node.js version increases

What's NOT a Breaking Change?

• Adding new tools
• Adding new optional configuration options
• Performance improvements
• Bug fixes that don't change expected behavior
• Documentation updates

Checking Your Version

# Check installed version
npx @byronwade/memoria --version

# Or if installed globally
memoria --version

Upgrading

When using npx, you always get the latest version:

npx @byronwade/memoria@latest

For global installations, update with:

npm update -g @byronwade/memoria