kill-claude-mem

Terminate stale claude-mem worker and MCP server processes via bash scripts.

23|4|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/reggiechan74/JobOps --skill kill-claude-mem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kill-claude-mem
Source: https://github.com/reggiechan74/JobOps/tree/main/.claude/skills/kill-claude-mem
Command: npx skills add https://github.com/reggiechan74/JobOps --skill kill-claude-mem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Kills stale claude-mem worker and MCP server processes that can linger across sessions, preventing memory bloat and slow Codespace performance.

Core Features & Use Cases

  • Provides a one-shot cleanup that terminates stale worker-service and mcp-server processes to reclaim memory.
  • Installs a SessionStart hook to automatically clean up on startup and resume, ensuring fresh instances.
  • Use case: in extended Codespaces or ephemeral environments where memory usage grows across sessions.

Quick Start

Run the kill-claude-mem.sh script to terminate stale claude-mem processes and let hooks respawn them on the next interaction.

Frequently Asked Questions about kill-claude-mem

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

FAQPage Schema
How do I kill stale claude-mem processes to free up memory in Codespaces?

Run the kill-claude-mem.sh script to terminate lingering worker-service and mcp-server instances, which reclaims memory in Codespace environments.

Why does claude-mem memory usage grow across sessions in ephemeral environments?

claude-mem memory usage grows because worker and MCP server processes accumulate across launches without terminating, causing memory bloat and slow Codespace performance.

Can I automatically clean up claude-mem processes on startup?

Yes, you can install a SessionStart hook to automatically clean up stale claude-mem processes on startup and resume, ensuring fresh instances respawn on the next interaction.

Do I need jq to run the claude-mem cleanup script?

Yes, jq is a required dependency for running the claude-mem cleanup script, as the bash scripts use it to identify and terminate specific processes deterministically.

What's the best way to prevent memory leaks from claude-mem worker processes?

Use a deterministic cleanup workflow with bash scripts to kill stale worker-service and mcp-server processes, optionally respawning fresh instances via a SessionStart hook.