​

Breaking Changes

​

Memory endpoints migrated to POST

• recall, answer, recall/as-of, recall/changed-since — now accept JSON request bodies instead of query parameters.
• memory_types renamed to type — accepts a list of strings across all recall endpoints and CLI recall commands.

​

Session and auth changes

• /session/current renamed to /status — requires no session token; reads active session from local state.
• /session/extend removed — session extension is no longer supported.
• /sessions list endpoint removed.
• Authorization header dropped for API key — MOORCHEH_API_KEY is read from server config only; Bearer header auth is removed.
• X-Session-Token is the only auth mechanism for per-request memory operations.

​

Legacy routes removed

• /api/v1/namespaces, /api/v1/memory, /api/v2/context — moved to memanto/app/legacy/.

​

New Features

​

Recall and conflict endpoints

• POST /{agent_id}/recall/recent — retrieves most recent memories without a query string; replaces /recall/current.
• GET /{agent_id}/conflicts — lists detected memory contradictions.
• POST /{agent_id}/conflicts/resolve — resolves a flagged contradiction.
• DELETE /agents/{agent_id}?delete-backup-too=true — optionally wipes the agent’s remote Moorcheh namespace on deletion.

​

Startup validation

• Fail-fast API key check — server validates MOORCHEH_API_KEY on startup and refuses to start if missing or authentication fails.

​

Improvements

​

Structured request body models

• Pydantic models (RecallRequest, RecallAsOfRequest, RecallChangedSinceRequest, RecallRecentRequest) with full field validation and bounds checking.
• Smart date defaults — date-only as_of defaults to end-of-day; since defaults to start-of-day, so full ISO datetimes are not required for daily windows.

​

Auth and session service

• get_moorcheh_api_key() reads from server config only — no per-request header parsing.
• verify_moorcheh_api_key() validates once at startup instead of on every request.
• extend_session() removed; moorcheh_api_key parameter removed from create_session(), validate_session(), and renew_session().

​

Health check

• /health no longer requires client dependency injection.
• Status reports "unhealthy" (was "degraded") when Moorcheh is unreachable.

​

CLI

• memanto session extend removed.
• “Activation” terminology replaces “session” across agent create, agent activate, agent deactivate, and memanto status.
• memanto status panel renamed to Active Agent (was “Active Session”).

​

UI Fixes

​

UI shutdown fix

• Server stability — fixed an issue where the API server would unexpectedly shut down when refreshing or closing the browser tab. The server now stays alive unless explicitly stopped or running in specific UI-only modes.

​

Tests

• Added tests/test_e2e.py with end-to-end API coverage.

​

Improvements

​

API input validation

• Content fields — remember, recall, answer, recall/as-of, recall/current, and recall/changed-since enforce min_length=1 on query/content fields and max_length=500 on title.
• Numeric bounds — confidence, min_similarity, threshold, and temperature bounded [0.0, 1.0]; limit enforced ge=1.
• CostGuard validators (validate_text_length, validate_query_length, validate_k_limit) applied across all memory read/write endpoints.

​

Session extension guard

• API — extending a session with additional_hours <= 0 now returns HTTP 422.
• CLI — memanto session extend rejects non-positive --hours values before sending the request.

​

Daily summary custom output path

• output_path parameter added to generate_summary() and generate_daily_summary().
• When provided, the summary Markdown file is written to the specified path; parent directories are created automatically.

​

Agent pattern options

• memanto agent create --pattern help text updated to list only available patterns: project, support, tool (removes unavailable chat, research, custom).

​

Dependencies

• moorcheh-sdk minimum version bumped from >=0.1.0 to >=1.3.5.

​

Bug Fixes

​

UI dashboard authentication

• Root cause — the masked API key was being used for backend authentication, causing all dashboard data to fail loading after login.
• Fix — restored transmission of the full API key in the configuration response so the dashboard can authenticate backend requests properly.
• Display — api_key_preview remains masked (........XXXXXX) in the settings tab; only the backend communication is affected.

​

Tests

• Full test suite: 54 passed. UI connectivity verified.

​

Improvements

​

API key verification

• First-run setup — memanto now actively verifies the key against Moorcheh before saving; invalid keys are rejected immediately; transient network issues surface as a warning rather than blocking setup.
• Lighter auth ping — verification switched from client.namespaces.list() to client.documents.get(...) against a sentinel namespace. NamespaceNotFound is treated as success (key authenticated; namespace simply doesn’t exist).
• Clearer error codes — auth dependency returns 401 on AuthenticationError and 500 on unexpected errors.

​

Server health check

• /health uses the same documents-based ping, so health reflects real authentication state.

​

Configurable summary model

• SUMMARY_MODEL setting (default anthropic.claude-sonnet-4-6) used for daily summary and conflict reports.
• ~/.memanto/config.yaml now supports memanto.summary.model, memanto.answer.model, temperature, and answer_limit — loaded at startup so models can be swapped without code changes.

​

UI security

• /api/ui/config and the API-key update endpoint now return a masked preview (••••••••<last6>) instead of the raw key — plaintext key is no longer sent to the browser.

​

Tests

• Full test suite: 54 passed.

​

Bug Fixes

​

Web UI authentication after CLI activation

• Dashboard, Memory Explorer, recall, and analytics views now load correctly after memanto agent activate.
• “Session may be expired” and “Activate an agent via CLI to explore memories” error states are resolved.

​

Improvements

​

Simplified first-run setup

• Single-step onboarding — memanto setup now prompts only for the Moorcheh API key.
• Removed the schedule time (HH:MM) prompt, related validation, and automatic ScheduleManager().enable(...) call from onboarding.

​

Improvements

​

Onboarding and documentation

• README quick start de-emphasizes memanto serve as a prerequisite — users can run memanto, create an agent, and try memories without keeping a local API process running.
• memanto serve documented as optional, for HTTP/REST use only.
• Agent integration guide shortens quick start to create → remember → recall, and updates Python examples.
• Session architecture doc notes that memanto agent create auto-activates in the CLI.

​

CLI output polish

• memanto status / memanto serve use Local REST API wording; healthy API shows online.
• Success messages drop the OK prefix across agent create, remember, upload, and daily summary flows.
• Welcome Quick Start lists memanto ui, reorders commands, and describes memanto serve as starting the local REST API.

​

memanto connect list

• Column renamed to Agent Name; rows show agent name instead of display_name.

​

Behavioral Changes

• memanto agent create already auto-started a session; docs and Quick Start now consistently reflect this so separate memanto agent activate is not shown as a required step.
• Default session/extension examples reference 6 hours where updated.

​

Tests

• Full test suite: 54 passed.

​

Improvements

​

CLI onboarding flow

• Quick start now shows memanto serve first and guides users to open a new terminal for agent commands.
• memanto serve prints a clear “next step” hint after startup.
• memanto agent create <agent-id> now starts a session automatically.

​

Documentation

• Updated README.md, docs/CLI_USER_GUIDE.md, docs/CLI_INSTALLATION.md, docs/AGENT_INTEGRATION_GUIDE.md.

​

Behavioral Changes

• memanto agent create auto-activates a session — separate memanto agent activate is usually not required in the quick start flow.

​

Tests

• Updated CLI tests for auto-session behavior. Full test suite: 54 passed.

​

Improvements

​

README branding

• Title updated to Memanto - Memory that AI agents love! to better capture what Memanto delivers to AI agents.

​

New Features

​

Semantic memory engine

• Agents — persistent identity with isolated memory namespaces (e.g. customer-support-bot, dev-assistant).
• Sessions — 6-hour active windows; memories persist forever and remain accessible across all future sessions.
• 13 memory types — fact, preference, decision, goal, instruction, event, and more, each stored with a confidence score.
• Zero-indexing semantic search — memories are available for retrieval the exact millisecond they are written; no indexing delay.
• State-of-the-art accuracy — 89.8% on LongMemEval, 87.1% on LoCoMo.

​

Memanto CLI

• pip install memanto — full memanto command-line interface with organized command groups: agent, memory, session, schedule, config, connect, and core utilities.
• Quickstart workflow:
  memanto                              # initial API key configuration
  memanto agent create my-agent
  memanto remember "Project kickoff is Monday" --type event
  memanto recall "When is project kickoff?"
  

​

REST API

• Full v2 HTTP API for agent lifecycle, session management, memory read/write, recall, and generative answers.
• Dual authentication — Authorization: Bearer <moorcheh-api-key> for all requests; X-Session-Token: <jwt> for memory operations.

​

Developer integrations

• 13+ AI coding assistants and IDEs — Claude Code, Cursor, Cline, Windsurf, Continue, GitHub Copilot, OpenCode, Goose, Roo, Antigravity, Augment, Gemini CLI, Codex.
• Connect via memanto connect <tool> with project-local or --global scope.

​

MemantoClaw

• Open-source reference stack combining OpenClaw, NVIDIA OpenShell, and Memanto memory.
• One-command provisioning — memantoclaw onboard configures inference routing, credentials, and memory bridge automatically.
• Enhanced security — stricter seccomp/Landlock policies, credential filtering, immutable gateway config, host-bridge memory architecture.