Greplica icon

Greplica

Open-source local memory for AI coding agents that stores repo decisions, constraints, gotchas, and session context.

Reviewed by ToolWorthy Editors·updated today

Pricing:100% Free
Jump to section
Greplica open-source engineering memory for AI coding agents

Featured alternatives

Claude Code icon

Claude Code

Cursor icon

Cursor

AILandscape.Design icon

AILandscape.Design

Claude icon

Claude

Gemini icon

Gemini

Pros & Cons

Pros

  • Solves a real pain in agentic development: repeated rediscovery of repo context
  • Open source and local-first design lowers privacy concerns
  • Works with Codex, Claude Code, and other agent workflows rather than locking into one IDE
  • Hybrid search is better suited to task-specific retrieval than one long memory markdown file
  • Useful even for solo developers maintaining multiple repos with recurring agent sessions

Cons

  • Memory quality depends on disciplined session updates
  • Incorrect negative knowledge, such as a stale failed approach, can mislead future agents if not reviewed
  • Team-wide shared memory introduces governance questions around provenance, expiry, and conflicting forks
  • Setup is more technical than a typical SaaS developer tool
  • Managed shared mode details and pricing are not yet fully public

Overview

Greplica is an open-source memory layer for AI coding agents. It stores the useful context that normally disappears between sessions: engineering decisions, constraints, gotchas, failed approaches, file-level notes, and repo-specific patterns. The goal is simple: when Claude Code, Codex, or another coding agent starts a new task, it can retrieve the relevant history instead of rediscovering the same context manually.

The product is aimed at teams already using AI coding agents for real engineering work. Static AGENTS.md or CLAUDE.md files are useful, but they become stale and cannot hold every decision from every agent run. Greplica turns that knowledge into a searchable graph so agents can ask for task-specific context before broad exploration.

Greplica is especially interesting because it is local-first and free. The public site positions it as open source, fully local, and usable without a new API key. That makes it a practical experiment for teams that want better agent continuity without sending private codebase memory to another hosted SaaS product.

Key Features

  • Persistent engineering memory - Saves useful decisions, constraints, gotchas, and repo context from coding sessions so future agent runs can start with prior knowledge.
  • Agent-native setup - Provides install flows for Codex, Claude Code, and OpenCode, so the memory workflow can be triggered from the same agent environment developers already use.
  • Hybrid retrieval - Combines keyword search, semantic search, and graph connections to return relevant context instead of dumping a long flat document into the prompt.
  • Self-updating wiki - Structures memory as linked nodes across components, flows, and decisions, helping the knowledge base grow as the repo changes.
  • Fully local storage - Stores memory on the developer machine, with the public site describing local storage under the user home Greplica database and no telemetry or cloud requirement for the local mode.
  • Open-source workflow - The code is public on GitHub, which matters for a tool that reads engineering context and influences future agent decisions.

How to Get Started

Greplica is a developer tool, so setup is closer to a CLI workflow than a SaaS onboarding screen.

  1. Install the CLI globally with npm.
  2. Run the installer for your agent platform, such as Codex or Claude Code.
  3. Choose local embeddings for a no-API-key setup, or switch later to OpenAI embeddings if you prefer hosted semantic search.
  4. Bootstrap the repo once so Greplica can build the initial graph.
  5. During future tasks, ask the agent to retrieve relevant Greplica context before broad manual exploration.
  6. At the end of useful sessions, update working memory so decisions and follow-up work are retained.

Teams should still keep a small Claude Code or AGENTS guidance file for critical operating rules. Greplica is best treated as a retrieval layer for detailed repo memory, not as the only source of mandatory instructions.

Pricing & Plans

Greplica is currently positioned as fully free and open source.

Plan Price Notes
Local open-source mode Free Runs locally, with no separate API key required when using local embeddings.
OpenAI embeddings Usage-based external cost Optional if teams switch from local embeddings to OpenAI embeddings. Greplica itself is still open source.
Managed shared mode Not publicly detailed Product Hunt mentions a managed shared mode, but public pricing details were not visible during this review.

For most solo developers, the meaningful cost is setup time. For teams, the cost question is whether they want a managed shared memory layer across developers, forks, and clones.

Best For

  • Engineering teams using Codex, Claude Code, OpenCode, or similar agents across the same repo
  • Developers maintaining large codebases where architectural context is expensive to rediscover
  • Teams that want a local-first alternative to hosted agent memory products
  • Solo builders who repeatedly return to projects after days or weeks away
  • Agent-heavy workflows where AI code review, refactoring, and implementation decisions need continuity

FAQ

What is Greplica?

Greplica is an open-source memory system for AI coding agents. It stores repo-specific engineering context and retrieves relevant notes for future tasks.

Does Greplica work with Codex?

Yes. The public install instructions include Codex, Claude Code, and OpenCode setup paths. It is positioned as agent-agnostic rather than tied to one assistant.

Is Greplica free?

Yes. Greplica is currently positioned as open source, fully local, and free to use. Optional hosted embeddings or managed sharing may introduce external costs or future paid tiers.

Where does Greplica store data?

The public site describes local storage under the user's Greplica graph database for the local mode. Teams should review the GitHub repo and configuration before using it with sensitive codebases.

Does Greplica replace AGENTS.md or CLAUDE.md?

Not completely. It can reduce dependence on large static docs, but mandatory workflow rules should still live in a small, explicit instruction file. Greplica is better for searchable, evolving context.

What is the biggest risk?

The main risk is stale or incorrect memory. Teams should pay attention to provenance, expired assumptions, and failed approaches that may no longer be true after refactors.

Is this your tool?

Upgrade this free listing to Verified to unlock all four below. One-time fee of $99.

Claim & upgrade

Verified badge

A blue Verified pill appears next to your tool name across ToolWorthy. Embeddable on your own site too.

Featured alternatives slot

Appear in the sidebar of similar tools' detail pages — intent-matched traffic from competitors.

Dofollow backlink

Your Visit Site button sends direct SEO value to your domain instead of nofollow.

Editor-curated review

We expand your listing with original pros/cons, use cases, and screenshots — on-brand and on-message.

From the blog

View all →

Track Greplica in ToolWorthy Weekly

Important tool updates, better alternatives, and selected AI signals in one weekly brief.

Weekly only. Unsubscribe anytime.