rune-echoes

Persist cross-session agent learnings to .claude/echoes with a 5-tier memory lifecycle.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune-plugin --skill rune-echoes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-echoes
Source: https://github.com/vinhnxv/rune-plugin/tree/main/plugins/rune/skills/rune-echoes
Command: npx skills add https://github.com/vinhnxv/rune-plugin --skill rune-echoes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents across sessions risk losing context and duplicating effort; Rune Echoes provides a centralized memory lifecycle to persist learnings, patterns, and decisions to .claude/echoes/.

Core Features & Use Cases

  • 5-tier memory lifecycle (Etched, Notes, Inscribed, Observations, Traced) with auto-pruning
  • Per-role MEMORY.md storage under .claude/echoes/ and automatic consolidation
  • Remember, read, and surface prior learnings during reviews, audits, planning, and execution

Quick Start

Activate echoes by initializing the echoes directory and start recording learnings with /rune:echoes remember.

Frequently Asked Questions about rune-echoes

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

FAQPage Schema
How do I persist agent memory across sessions to avoid losing context?

Agent memory persistence works by saving learnings to a `.claude/echoes` directory using a 5-tier lifecycle (Etched, Notes, Inscribed, Observations, Traced) with automatic consolidation and per-role MEMORY.md storage.

What is the best way to manage cross-session agent memory and prune outdated context?

Managing cross-session agent memory is best handled through a 5-tier lifecycle system that automatically prunes outdated context and consolidates learnings into per-role MEMORY.md files under a dedicated echoes directory.

How do I start recording agent learnings and decisions for future planning sessions?

To start recording agent learnings, initialize the echoes directory and use the `/rune:echoes remember` command; this captures decisions and patterns to surface them automatically during future planning and execution.

Can I use cross-session memory to surface prior patterns during code reviews and audits?

Yes, cross-session memory is specifically designed to be used during code reviews and audits, surfacing prior patterns and guidance by reading from the persisted learnings stored in the `.claude/echoes` directory.

Does the agent memory lifecycle support role-specific context storage?

The agent memory lifecycle supports role-specific context storage by maintaining individual MEMORY.md files under the `.claude/echoes/` directory, ensuring learnings are consolidated and organized per role.

When should I use a 5-tier memory lifecycle over simple session logs?

A 5-tier memory lifecycle is ideal when agents risk duplicating effort across sessions and need structured auto-pruning and consolidation, whereas simple session logs lack automatic context surfacing during audits and planning.