init-memory

Initialize Vestige session context by calling the mcp__vestige__session_context tool.

4|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/alphaleonis/decaf-claude-config --skill init-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-memory
Source: https://github.com/alphaleonis/decaf-claude-config/tree/main/decaf-memory/skills/init-memory
Command: npx skills add https://github.com/alphaleonis/decaf-claude-config --skill init-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a manual fallback to load Vestige session context when the automatic startup hook fails to trigger the necessary session_context call.

Core Features & Use Cases

  • Manual Session Initialization: Allows users to explicitly load Vestige memory context.
  • Troubleshooting: Useful when the automatic memory loading mechanism doesn't work as expected.
  • Use Case: If Claude Code restarts and doesn't seem to have access to your previous conversation history or user preferences, you can use this skill to manually re-establish that connection.

Quick Start

Call the session_context tool with broad queries and the current project context.

Frequently Asked Questions about init-memory

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

FAQPage Schema
How do I manually load Vestige session context when startup hooks fail?▼

Manually load Vestige session context by triggering this skill to call the `mcp__vestige__session_context` tool, restoring access to user preferences, instructions, and feedback.

Why does Claude Code not remember my previous conversation history after a restart?▼

Claude Code loses conversation history after a restart when automatic session startup hooks fail to load Vestige memory context, requiring a manual fallback initialization to restore previous session state.

Do I need the Vestige MCP server connected to manually initialize session context?▼

Yes, manually initializing Vestige session context requires the Vestige MCP server to be actively connected and accessible to successfully execute the `mcp__vestige__session_context` tool call.

What is the best way to restore user preferences and feedback when automatic memory loading fails?▼

The best way to restore user preferences and feedback during memory loading failures is to use a manual fallback skill that explicitly calls the Vestige session context tool with broad queries and project context.

Can I use session context initialization as a fallback for troubleshooting memory loading?▼

Yes, you can use manual session context initialization for troubleshooting when the automatic Vestige memory loading mechanism fails to trigger, ensuring your instructions and preferences remain available.