This release introduces auto-spawning for child workers when a workspace changes, significantly streamlining development workflows. It also implements an idle TTL to ensure resource efficiency by cleaning up inactive workers. These changes improve overall system responsiveness and resource management under load.

We've introduced a new architecture for the broker to spawn dedicated child servers for each workspace dynamically. These workers now automatically handle idling and cleanup via a configurable TTL, ensuring resources are efficiently managed as workspace contexts shift. This change streamlines developer workflows by automating server lifecycle management based on current project access.

This update adds comprehensive testing for the remaining MCP tools, including repository operations and memory management functionality. These tests ensure consistent behavior across indexing, searching, and note storage tools. Ensuring these tools are reliable helps maintain a robust interface for repository interactions.

This release adds the MEMENTO_CHANGE_DETECTOR environment variable, allowing users to explicitly configure how the server monitors repository changes. You can now choose between auto (filesystem watcher first, with fallback to Git polling for Git repos), fs (force filesystem watcher), or git (force Git status polling) to better suit your development environment. This update also improves the robustness of workspace switching and includes stability fixes for the VS Code extension installation process.

We've inverted the change detection strategy to prioritize filesystem watchers over Git status polling, which provides faster and more responsive updates. Added the MEMENTO_CHANGE_DETECTOR environment variable to allow users to force specific strategies or stick with the new auto default, which safely falls back to Git polling if the watcher fails.

Updated the CI workflow used to maintain the server/latest release tag to correctly resolve the associated commit SHA after checking out the source tag. This ensures that the release points to the proper snapshot of the repository, preventing packaging and release issues. This change improves the reliability of our automated release pipeline.

Updated the move-server-latest workflow to trigger automatically on server/v* tag pushes. This ensures that every server release is now correctly mirrored to the server/latest tag and release, streamlining the delivery pipeline for server binaries and installable packages.

This update fixes an issue where the VS Code extension failed to correctly resolve the latest server release tag during installation. By adding a dedicated check for the latest non-draft, non-prerelease server tag, the extension now more reliably fetches the correct binary version. Integrators will notice fewer installation errors when using default configuration settings.

This update changes how the VS Code extension discovers the latest server binary. Instead of relying on GitHub’s generic 'latest' release, it now dynamically probes for the most recent release tagged with the server/v* prefix. This ensures users are more reliably matched with compatible binary versions while maintaining a fallback to manual source builds.

This release adds the repo_switch_workspace tool, enabling MCP servers to retarget to different directories without requiring a process restart. We've also included initial support for Python import graphs to improve context-awareness and updated the VS Code extension with automated workspace switching. These changes significantly improve development agility by reducing the need for constant server cycling.

This release introduces repo_switch_workspace, allowing the MCP server to retarget its working directory without restarting the process. We've also added Python import graph support to repo_related_files and streamlined installation workflows. These changes improve performance for multi-repo workflows and provide deeper context for Python projects.

This update introduces dynamic workspace switching, allowing the server to rebind to new roots at runtime and isolating index/memory contexts accordingly. I've also added VS Code support for auto-switching and included a fallback mechanism for extension installations, streamlining development across multiple repositories. These changes significantly improve how the system handles context shifts, with unit tests now covering the isolated memory state.

This release adds Python import graph support to repo_related_files, enabling better context retrieval for Python codebases. We've also introduced a new memento-mcp setup CLI command to simplify configuration across VS Code, Cursor, Claude Desktop, and Windsurf, and added robust cache invalidation for JS/PHP import graphs. Additionally, internal test coverage reporting is now enforced for high-stakes packages to ensure continued codebase stability.

Updated the extension release workflow to move the VSCE_PAT secret reference to a job-level environment variable. This cleans up the workflow configuration and provides a more consistent way to validate secret availability before running the publishing step. This ensures smoother releases for the VS Code extension.

This release aliases server/latest to v0.5.0, bringing significant improvements to our repository context tools, including intent-aware routing for Navigate, Implement, and Review workflows. We've simplified installation with a new setup CLI command that automatically detects and configures your IDE, added support for per-workspace child server spawning, and improved our binary packaging for Linux and macOS. These changes ensure a smoother onboarding experience and more effective AI-assisted code navigation.

This release introduces intent-aware repo_context routing for clearer navigation and implementation workflows, alongside new outline/summary output modes to significantly reduce context buffer consumption. We've also added convenience CLI helpers (print-config, print-guidance) and improved release automation to better support generic and VS Code-based MCP clients. These changes enable more efficient context management for LLM-driven coding tasks.

This release adds intent-based routing to repo_context (navigate, implement, review), allowing users to obtain optimized context shapes (outlines vs. full source) automatically. We've also added built-in outline and summary extractors for Go, JS, and TS, alongside new CLI commands (print-config, print-guidance) to improve integration. These changes streamline LLM interactions by simplifying the path to finding relevant code without manual mode-switching.

Added an intent field to the repo_context tool, allowing LLMs to request context specifically for navigate, implement, or review tasks. This maps to optimized internal output modes, while explicit mode usage remains supported for advanced overrides. Additionally, the tool now suggests logical follow-up calls in its response to facilitate deeper file exploration.

We've enhanced the repo_context tool by adding support for different output modes: full, auto, outline, and summary. The new 'auto' mode intelligently balances detail by providing full chunks for the target file while including outlines for related files, all supported by new language-specific (Go/JS/TS) outline extractors. Additionally, we've improved efficiency with path-based exclusions and chunk deduplication.

The release pipeline has been updated to automatically build and upload platform-specific packages (.deb for Linux and .pkg for macOS) alongside raw binaries. Additionally, new Makefile targets provide a streamlined CLI interface for cutting versioned releases. These changes reduce manual effort and improve distribution support across operating systems.