Greplica

Persistent, searchable engineering memory for AI coding agents

Does your coding agent spend 5 minutes just grepping around when you give it a complex task?

That's because it is re-learning context. Every new session, your agent wastes tokens and time building context on work it already did. And still misses important facts.

Greplica explores your repo structure, code and session transcripts to give your agent a persistent, maintained memory it can query before exploring. Local mode stays fully local with no telemetry; managed mode connects an authorized repository to shared team memory.

Agent Quick Start

Most users should not install Greplica by hand. Paste this into your coding agent from inside the repo you want Greplica to remember.

Greplica requires Node.js 22-26.

Full prompt: docs/agent-install-prompt.md

That prompt runs a short setup questionnaire, installs Greplica in local or managed mode, and either creates the first local context or connects to existing shared memory.

To visualize your current memory in a browser, run:

Shared Managed Memory

Managed mode lets contributors on different clones and forks query the same repository memory. It requires Greplica 0.2.0 or later and access to a managed Greplica server.

After an administrator invites your GitHub user to an organization or repository, run:

An organization admin can instead create one reusable, repository-scoped reader link from a folder already connected to the memory:

Give the printed link or command to an agent. It logs in when needed, claims access, installs Greplica, and upgrades local memory to the invited managed memory:

The link works for multiple GitHub users until an admin revokes it. Greplica never creates a new managed-memory namespace through this link. When ordinary managed…