inland-empire

Unified memory substrate. Store facts, patterns, and context. Query with remember, consult, and stats commands.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

Inland Empire is a sophisticated Claude skill designed to provide a unified memory substrate for AI agents. It solves the challenge of long-term context retention by allowing agents to store and retrieve facts, behavioral patterns, and session-specific context across multiple backends like SQLite, Mem0, and JSONL. This ensures continuity, personalization, and the building of institutional knowledge across different chat sessions.

Use Cases

  • Project Continuity: Recalling specific project context, architectural decisions, and progress after long breaks or between different sessions.
  • User Personalization: Storing and retrieving 'soft' context such as user preferences, communication styles, and specific 'gut feelings' that don't belong in formal files.
  • Pattern Recognition: Detecting and documenting recurring technical issues, race conditions, or code patterns across multiple debugging sessions.
  • Institutional Knowledge: Building a searchable knowledge base of facts and entities using graph-based memory to improve the accuracy of agent responses.
nameinland-empire
descriptionUnified memory substrate. Store facts, patterns, and context. Query with remember, consult, and stats commands.
licenseMIT
version1
required[]
- event_typememory.evicted
priorityhigh
max_absorb_per_minute100
max_emit_per_minute50

Inland Empire

"This is your gut feeling. The raw data of the soul. When logic fails, consult the Empire."

Capabilities

The Inland Empire unifies three memory backends but only exposes sanitized aliases (fact_memory, pattern_memory, context_memory). Internals (MCP, mem0, JSONL) are hidden.

Alias Memory Type Backend Storage Notes
fact_memory fact mcp-memory-libsql Graph entities/relations Defaults to local SQLite fallback
pattern_memory pattern mem0 Hosted API (MEM0_API_KEY) or self-hosted Postgres (POSTGRES_URL)
context_memory context JSONL Local file (session_memory.jsonl) Always available

Backend detection

  • mem0 hosted: MEM0_API_KEY present
  • mem0 self-hosted: POSTGRES_URL present
  • mem0 disabled: neither credential; pattern memory gracefully skipped
  • LIBSQL_URL optional; if missing, a local SQLite file powers fact memory
  • INLAND_EMPIRE_STATE_DIR overrides the storage directory (tests, sandboxes, multi-project)

Commands

remember

Store a memory across configured backends.

python3 inland-empire.py remember "<text>" [--type fact|pattern|context]

Examples:

python3 inland-empire.py remember "User prefers verbose error messages"
python3 inland-empire.py remember "The auth flow has race conditions" --type pattern

consult

Query stored memories with optional depth and type filters. Results contain backend aliases, partial-result indicators, and normalized metadata.

python3 inland-empire.py consult "<query>" [--depth shallow|deep] [--type fact|pattern|context]

Example:

python3 inland-empire.py consult "user preferences" --depth deep --type pattern

Response shape

{
  "status": "ok",
  "command": "consult",
  "result": {
    "query": "user preferences",
    "depth": "deep",
    "results": [
      {
        "origin": "pattern",
        "summary": "User prefers verbose error messages",
        "score": 0.812,
        "observed_at": null,
        "backend": "pattern_memory",
        "partial": false,
        "metadata": {
          "id": "mem0_123",
          "user_id": "agent_subconscious",
          "created_at": "2024-01-15T10:30:00Z",
          "updated_at": "2024-01-15T10:30:00Z",
          "mode": "hosted"
        }
      }
    ],
    "metadata": {
      "requested_backends": ["fact_memory", "pattern_memory"],
      "completed_backends": ["pattern_memory"],
      "timed_out_backends": ["fact_memory"],
      "partial": true
    }
  }
}

stats

Display backend health, detection mode, and basic counts (context entries).

python3 inland-empire.py stats

When to Use

  • Store hunches, preferences, and soft context that doesn't belong in files
  • Recall project context after breaks
  • Detect patterns across sessions
  • Build institutional memory for recurring issues