hmem-setup

Configure the hmem memory system and MCP server for AI tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-setup-yuryzzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmem-setup
Source: https://github.com/YuryZZZ/opencode-global/tree/main/skills/hmem-setup
Command: npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-setup-yuryzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Install and configure the hmem memory system to enable persistent memory for AI agents across tools, including auto-memory hooks and per-tool setups.

Core Features & Use Cases

  • Auto-detects installed tools (Claude Code, Gemini CLI, OpenCode) and configures memory integration.
  • Creates and configures the memory directory, .mcp.json, and hmem.config.json.
  • Installs and wires up memory hooks and copies skill files to tools' skill directories.
  • Supports first-time setup, manual installation, and post-setup verification across supported tools.

Quick Start

Install hmem globally, run hmem init, and install the slash-command skills to complete the setup.

Frequently Asked Questions about hmem-setup

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

FAQPage Schema
How do I set up persistent memory for AI agents across multiple coding tools?

To set up persistent memory, this system auto-detects installed tools like Claude Code, Gemini CLI, and OpenCode, creates a memory directory, and generates the necessary MCP and configuration files to enable cross-tool memory hooks.

What does MCP server integration do for AI memory management?

MCP server integration connects your AI tools to a shared memory system by generating a .mcp.json file, wiring up auto-memory hooks, and ensuring persistent context is available across supported coding environments.

Can I configure memory hooks for Claude Code, Gemini CLI, and OpenCode at the same time?

Yes, the setup process auto-detects installed tools and configures per-tool memory integration simultaneously, copying skill files to each tool's skill directory and applying specific configurations for Claude Code, Gemini CLI, and OpenCode.

What steps are required to configure the hmem memory system from scratch?

The configuration steps include tool detection, memory directory creation, .mcp.json generation, hmem.config.json creation, and deploying skill files to the respective tool directories to activate auto-memory hooks.

Do I need to manually configure files to enable auto-memory hooks in my coding environment?

No, running the initialization command automatically creates the memory directory, generates the required .mcp.json and hmem.config.json files, and wires up memory hooks without manual file editing.

How do I verify my memory system setup is working correctly after installation?

Post-setup verification checks that the memory directory exists, .mcp.json and hmem.config.json are correctly generated, and auto-memory hooks are properly deployed across detected tools to ensure persistent memory is active.