mxSave

Name: mxSave
Availability: InStock
Author: microtronx

Persists mxLore session state and synchronizes orchestrate-state.json data across sessions.

29|8|Updated Apr 6, 2026

Search Tags:#claude-md #session-end #session-notes #save-state #orchestrate-state #mcp-db

Ready to run

npx skills add https://github.com/MicrotronX/mxLore --skill mxsave

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mxSave
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxSave
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxsave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The mxSave skill ensures reliable preservation of the current mxLore session state across sessions, enabling safe resume, audit trails, and cross-session continuity by persisting settings, notes, and delta information.

Core Features & Use Cases

Persist project state at session end, including last_save_summary, last_save_session_note_doc_id, and reconciled deltas.
Create and update session notes and related documents in the MCP-DB, CLAUDE.md, and status.md, with robust write safety.
Optional hybrid synchronization of orchestrate-state.json and in-memory deltas to support loop mode, restarts, and cross-agent coordination.

Quick Start

Invoke /mxSave at session end to persist the current mx-project state, update CLAUDE.md/status, and create session notes.

Frequently Asked Questions about mxSave

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I save session state and notes when wrapping up a coding session?▼

To save session state at wrap-up, invoke the save command to persist current settings, notes, and delta information. This process updates CLAUDE.md, status.md, and the MCP-DB, ensuring stable notes for cross-session continuity.

What is the best way to persist CLAUDE.md status updates across multiple sessions?▼

The best way to persist CLAUDE.md status updates is through deterministic initialization and in-memory delta reconciliation during session wrap-up. This enforces safe writes to state files, ensuring reliable resume and audit trails.

Can I synchronize orchestrate-state.json for cross-agent coordination during restarts?▼

Yes, you can synchronize orchestrate-state.json using hybrid synchronization during wrap-up. This supports loop mode, restarts, and cross-agent coordination by reconciling in-memory deltas and safely writing to state files.

How does session state persistence handle delta reconciliation in MCP-DB?▼

Session state persistence handles delta reconciliation by applying deterministic initialization and reconciling in-memory deltas at session termination. It safely writes reconciled deltas, session notes, and related documents to the MCP-DB.

When should I trigger a session wrap-up save to ensure safe resume?▼

You should trigger a session wrap-up save during session termination, hybrid-mode saves, or before restarts. This ensures last_save_summary, session notes, and orchestrate-state data are safely written for seamless resume.