MemWhale
Description
Persistent, local memory for developers and their coding agents. Records commands, output, errors, and the fixes that worked into SQLite and serves them over MCP.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
MemoryWhale
Persistent local debugging memory for developers and coding agents.
简体中文 README · 繁體中文 README · 한국어 README · 日本語 README
MemoryWhale records what actually happened while you debug: commands, output, failures, and the fixes that worked. It stores that evidence in local SQLite so you and your coding agents can find it after the terminal, SSH connection, or agent session is gone.
Why MemoryWhale
- Remember what actually happened. Preserve the command, environment, output, failure, and lesson—not only a shell-history line.
- Use one memory across coding agents. Any compatible stdio MCP client can
read and write the same local memory through
mw-mcp. - Keep development history local. MemoryWhale works without an account, hosted service, or per-token memory bill.
MemoryWhale records development experience, not everything. It is a debugging memory layer, not an auton
Related Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.