Greplica icon

Greplica

Beanspruchen

Greplica gives AI coding agents persistent, searchable repository memory to reuse context across sessions, with local and managed modes.

Greplica

Persistent engineering memory for coding agents

Greplica is a developer tool for AI coding agents that aims to preserve engineering context across sessions. Its README describes it as a persistent, searchable engineering memory that helps agents avoid re-learning the same repository context, especially on complex tasks.

The product builds memory from repository structure, code, and session transcripts, then lets an agent query that memory before doing more exploration. The source also distinguishes between a fully local mode with no telemetry and a managed mode that connects an authorized repository to shared team memory.

Core capabilities

Persistent repository memory

Greplica builds a persistent memory from repo structure, code, and session transcripts so the agent can query prior work instead of re-grepping the same repository context every session.

Searchable context lookup

The README describes a query-first workflow where the agent can ask Greplica for context before exploring the codebase on its own, which is meant to reduce repeated context gathering.

Local-only operation

Local mode keeps data fully local and, according to the README, does not send telemetry. That makes it suitable when teams want repository memory without server-side sharing.

Shared managed memory

Managed mode connects an authorized repository to shared team memory, allowing contributors on different clones and forks to query the same repository memory.

GitHub Actions reconciliation

The package includes a GitHub Action that audits a Memory PR against an exact merge SHA and attests the result with GitHub OIDC.

Graph view and context commands

The README documents graph inspection commands, including a browser graph view and graph context queries, for viewing and retrieving stored memory.

Practical use cases

  • Reduce repeated context building

    Use Greplica when an AI coding agent keeps re-deriving the same repository facts across sessions. The memory layer is meant to give the agent a persistent place to look up prior context first.

  • Shared team memory across clones and forks

    Use managed mode when multiple contributors, including people on forks or separate clones, need to query the same repository memory. The README says managed memory is shared across contributors with authorized access.

  • Keep memory local to a workstation

    Use the local mode when you want repository memory to remain on the machine and avoid telemetry. The README describes local mode as fully local.

  • Audit managed memory updates in GitHub Actions

    Use the GitHub Action when a managed repository needs a reproducible reconciliation step against an exact merged commit. The action is built to audit a Memory PR and attest the result with GitHub OIDC.

  • Inspect and query stored context

    Use graph view or graph context commands when you need to inspect what memory Greplica has stored or retrieve focused answers about the repository. The README shows browser and CLI-based graph commands for this purpose.

Pros and Cons

Pros

  • Persists repository context across sessions instead of forcing agents to rebuild it repeatedly.
  • Can search and query stored context before the agent starts exploring code.
  • Supports a fully local mode with no telemetry, according to the README.
  • Supports managed shared memory for teams working across clones and forks.
  • Includes a GitHub Actions workflow for reconciling memory against an exact merge commit.

Cons

  • The README says Greplica requires Node.js 22-26, so it has a specific runtime requirement.
  • Managed mode depends on access to a managed Greplica server and an administrator-controlled repository or organization setup.
  • The source is documentation-heavy and workflow-specific, so teams will need to follow the published install and reconciliation steps rather than treating it as a plug-and-play UI app.

FAQ

How do you set up Greplica?

Greplica offers an agent-facing setup flow that starts from a prompt inside the repository you want it to remember. The README says most users should paste the provided install prompt into their coding agent, and that prompt runs a short questionnaire before installing Greplica in local or managed mode.

What does Greplica store and search?

The README states that Greplica explores repo structure, code, and session transcripts to build persistent memory. It can then be queried before the agent starts exploring the codebase again.

What is the difference between local mode and managed mode?

Managed mode is designed for contributors on different clones and forks to query the same repository memory. The README notes that local mode stays fully local with no telemetry, while managed mode connects to an authorized repository and shared team memory.

Is there a GitHub Actions integration?

The published workflow in action.yml is a composite GitHub Action named "Reconcile Greplica memory." It checks out the exact merge commit, sets up Node.js 22, and runs a CLI command to reconcile memory against a managed repository UUID.

What are the basic requirements for using Greplica?

The README says Greplica requires Node.js 22-26. For managed mode, it also requires access to a managed Greplica server and uses GitHub's browser device flow for login.

Quick Facts

Category
Developer Tool
Source domain
github.com
Primary users
AI coding agents and developers working with them
Runtime requirement
Node.js 22-26
Modes
Local and managed
GitHub integration
Composite GitHub Action and CLI commands