Eywa Continuum — Development skill for Claude Code

Eywa MCP

**Cross-session memory for Claude Code (MCP server + CLI).**

[](#) [](#) [](LICENSE)

The Problem

Claude Code sessions are ephemeral. Context is lost between sessions, so you start fresh each time and re-explain what you were working on.

For heavy Claude Code users with hundreds of sessions, that context reset becomes a major productivity drain.

The Solution

Eywa extracts a structured handoff at the end of each session and retrieves relevant past context at the start of the next one.

The name comes from the neural network in Avatar: Eywa connects sessions the way Eywa connects living memory.

How It Works

Eywa runs a deterministic pipeline around your Claude Code transcripts:

1. Session Detection: 4-strategy fallback (explicit session ID, PID tracing, CWD mtime, global mtime).
2. Session Conversion: JSONL transcript -> normalized markdown conversation.
3. Extraction: LLM-powered structured handoff extraction.
4. Indexing: Inverted index with metadata + TF-IDF-friendly keyword/project maps.
5. Retrieval: Query keyword scoring + recency decay to return relevant handoffs.

Claude Code JSONL Session
          |
          v
 [Session Detection]
          |
          v
 [JSONL -> Markdown]
          |
          v
 [Structured Extraction]
          |
          v
 [Handoff Markdown + Index]
          |
          v
      eywa_get()

Two-Stage Setup

Stage 1: Batch Index (one-time setup)

Use `eywa-batch` to process existing historical sessions in bulk through **OpenRouter**.

• You can pick any OpenRouter model (Gemini Flash, Claude, GPT, Llama, etc.)

• Default batch model: `google/gemini-3-flash-preview`

• Designed for hundreds of prior sessions

• Fast + low-cost extraction pass

• Builds your initial handoff corpus and index

Stage 2: Runtime