npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentic-eng/memory

v0.2.4

Published

Memory implementations for the EASA framework.

Readme

@agentic-eng/memory

Memory implementations for the Agentic Engineering Framework.

npm License: MIT TypeScript


Part of the Agentic Engineering Framework

The Agentic Engineering Framework is a minimal, type-safe TypeScript framework for building LLM-powered agent systems. It provides building blocks for agents that can reason, use tools, persist knowledge, and emit observable events — with zero LLM lock-in.

| Package | Description | | --- | --- | | @agentic-eng/agent | Agent class and reasoning loop — start here | | @agentic-eng/core | Shared types, enums, and error classes | | @agentic-eng/provider | Interface-only contracts (LlmProvider, MemoryProvider, ObservabilityProvider) | | @agentic-eng/tool | Tool interface and ToolRegistry | | @agentic-eng/memory (this package) | Memory implementations (FlatFileMemory) | | @agentic-eng/observability | Observability implementations (ConsoleObserver, NoopObserver) |


What This Package Does

@agentic-eng/memory provides concrete implementations of the MemoryProvider interface from @agentic-eng/provider. Memory allows the agent to persist knowledge across invocations — the LLM decides when to store information during the reasoning loop.

Currently ships:

  • FlatFileMemory — persists knowledge as KNL DATA blocks in flat files

Installation

npm install @agentic-eng/memory

Prerequisite: You also need @agentic-eng/agent to use memory with an agent.


Using FlatFileMemory with the Agent

import { Agent } from '@agentic-eng/agent';
import { FlatFileMemory } from '@agentic-eng/memory';

const agent = new Agent({
  name: 'assistant',
  provider: myProvider,
  memory: new FlatFileMemory({ directory: './agent-memory' }),
});

// The agent will now persist knowledge automatically
const result = await agent.invoke('Remember that my birthday is March 15th');
// → Stores a memory entry in ./agent-memory/assistant.memory.knl

const later = await agent.invoke('When is my birthday?');
// → Retrieves stored memories and uses them in context

How It Works

Each agent gets its own .knl file in the specified directory:

  • store(agentName, entry) — appends a KNL DATA block to {agentName}.memory.knl
  • retrieve(agentName) — parses all KNL blocks from the file back into MemoryEntry[]

Memories are stored as KNL DATA blocks:

<<<
KNL[DATA][1.0]:::
ID[knl:data:easa.memory:assistant:1710532800000:v1.0]:::
NS[easa.memory]:::
LABEL["User birthday"]:::
TAGS[personal,birthday]:::
ITEM["User's birthday is March 15th."] [DESC:"User birthday"]
>>>

Building a Custom Memory Provider

Need a database, vector store, or Redis backend? Implement the MemoryProvider interface from @agentic-eng/provider:

import type { MemoryProvider, MemoryEntry } from '@agentic-eng/provider';

class PostgresMemory implements MemoryProvider {
  async store(agentName: string, entry: MemoryEntry): Promise<void> {
    // INSERT INTO memories (agent, label, content, tags) VALUES (...)
  }

  async retrieve(agentName: string): Promise<MemoryEntry[]> {
    // SELECT * FROM memories WHERE agent = agentName
    return rows.map(r => ({ label: r.label, content: r.content, tags: r.tags }));
  }
}

// Use it the same way
const agent = new Agent({
  name: 'assistant',
  provider: myProvider,
  memory: new PostgresMemory(),
});

How It Fits Together

@agentic-eng/core (types + errors)
    ↑
@agentic-eng/provider (interfaces: LlmProvider, MemoryProvider, ObservabilityProvider)
    ↑
@agentic-eng/tool (Tool interface + ToolRegistry)
@agentic-eng/memory (FlatFileMemory — implements MemoryProvider)  ← you are here
@agentic-eng/observability (ConsoleObserver — implements ObservabilityProvider)
    ↑
@agentic-eng/agent (Agent class — composes everything)

Feedback & Contact

Have questions, feedback, or ideas? We'd love to hear from you:

License

MIT