Skip to content
Back to search

rekal-dev

MarketplaceWorks with Claude CodeGitHub

Rekal — memory of prior AI sessions, stored in git.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/rekal-dev/rekal-cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/rekal-dev/rekal-cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/rekal-dev--rekal-cli/badge.svg)](/listings/rekal-dev--rekal-cli)

HTML

<a href="/listings/rekal-dev--rekal-cli"><img src="/api/listings/rekal-dev--rekal-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**Requirements:** git, and macOS on Apple Silicon or Linux (x86-64 / arm64). Nothing else — no runtime, no Python, no API key, no service to run.

> **Status: 1.0.** The store format, wire format, command surface and exit > codes are covered by the version number, and breaking any of them now > requires a major version. [docs/compatibility.md](docs/compatibility.md) > states exactly what that covers and what it deliberately does not — > ranking and `index.db` stay unfrozen so retrieval can keep improving.

The binary is **~170 MB** to download and **~200 MB** on disk. That is the tradeoff for a single file: the inference engine, the embedding model, the database, and the full-text extension all ship inside it, so there is no model download on first run, no service to start, and recall works offline.

From Claude Code

/plugin marketplace add rekal-dev/rekal-cli
/plugin install rekal@rekal-dev

Then `/rekal:install` once per machine, and `/rekal:init` in each repo you want memory in. Both confirm before touching anything. That's the whole setup — skip to step 3 below.

From a shell

# 1. Install (into ~/.local/bin)
curl -fsSL https://raw.githubusercontent.com/rekal-dev/rekal-cli/main/scripts/install.sh | REKAL_VERSION=v1.0.2 bash

# 2. Turn it on in your repo
cd your-project
rekal init

# 3. Work as normal — commit, and your AI session is captured automatically
git commit -m "…"

# 4. In any later session, ask
rekal "why did we drop batching?"

<details> <summary>Other ways to install</summary>

**Read the script before running it** — same result, nothing piped into a shell:

curl -fsSL https://raw.githubusercontent.com/rekal-dev/rekal-cli/main/scripts/install.sh -o rekal-install.sh
less rekal-install.sh
REKAL_VERSION=v1.0.2 bash rekal-install.sh

**Download the binary yourself** from [Releases](https://github.com/rekal-dev/rekal-cli/releases/latest) — `rekal_darwin_arm64.tar.gz`, `rekal_linux_amd64.tar.gz`, or `rekal_linux_arm64.tar.gz`. Each release ships `checksums.txt`; verify with `shasum -a 256 -c checksums.txt`, then extract `rekal` onto your `PATH`.

**Install somewhere else** with `--target <dir>`. Piping into a shell needs `-s --` before it, because the flags are for the script, not for bash:

curl -fsSL https://raw.githubusercontent.com/rekal-dev/rekal-cli/main/scripts/install.sh | REKAL_VERSION=v1.0.2 bash -s -- --target /usr/local/bin

**Choose a different version** by changing `REKAL_VERSION`, or drop it to take whatever is newest:

curl -fsSL https://raw.githubusercontent.com/rekal-dev/rekal-cli/main/scripts/install.sh | bash

Without it the installer looks the newest release up over the network. The commands above name a version because that lookup is the one step that can fail on a network you do not control — a shared office IP can exhaust GitHub's 60 unauthenticated API calls an hour, and some proxies allow `github.com` but not `api.github.com`. A named version skips the lookup entirely.

`REKAL_VERSION` has to go in front of the command that runs the *script*. In front of `curl` it applies to the download and never reaches the script, which then resolves the newest version anyway.

**Build from source** if you want to change it. `go install` alone will not work, because the deep-embedding layer is CGO bound to a pinned llama.cpp build. Follow [docs/DEVELOPMENT.md](docs/DEVELOPMENT.md), which has the exact prerequisites (mise, git-lfs, cmake, the pinned llama.cpp tag).

</details>

`rekal init` sets up `.rekal/` (the store), a `post-commit`/`pre-push` git hook, the agent skill under `.claude/skills/rekal/`, an **orphan branch** `rekal/<your-email>` for transport (a branch with no common ancestor with your code, so it never touches your history, merges, or working tree), and one marker-tagged line in `CLAUDE.md` pointing your agent at the skill — plus the equivalent line in the rules file of

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 28 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-plugin-marketplace.json",
  3. "name": "rekal-dev",
  4. "description": "Rekal — memory of prior AI sessions, stored in git.",
  5. "owner": {
  6. "name": "Rekal"
  7. },
  8. "plugins": [
  9. {
  10. "name": "rekal",
  11. "source": "./plugin",
  12. "displayName": "Rekal Memory",
  13. "description": "Memory for your coding agent. Rekal saves every AI session transcript raw and append-only — no summaries to rot — then recalls the reasoning behind any change: why an approach was chosen, what was tried, what was rejected. Agent agnostic: Claude Code, Cursor, Codex, Gemini, Copilot, Kiro and OpenCode sessions all land in one ledger. Retrieval reasons at query time over the real record, with keyword and semantic search running locally — embedding is local, so there is no server, no account, no external memory service. Git is the transport: memory travels with your repo on push and reaches your team when work merges. Persistent cross-session context that maintains itself.",
  14. "homepage": "https://rekal.dev/",
  15. "repository": "https://github.com/rekal-dev/rekal-cli",
  16. "license": "Apache-2.0",
  17. "category": "memory",
  18. "keywords": [
  19. "memory",
  20. "recall",
  21. "git",
  22. "sessions",
  23. "context",
  24. "ledger"
  25. ]
  26. }
  27. ]
  28. }
README.md · README · 72 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Rekal — Git-backed memory for AI coding agents
  2. **Carry the context forward.**
  3. Ask your agent to Rekal context from your team and past work for the task at hand.
  4. Across sessions, agents and teammates—with the original sources ready to read.
  5. Rekal captures conversations and native memory-note revisions with commits,
  6. indexes them locally, and shares eligible project context through Git.
  7. One binary. Local embeddings by default. No hosted memory account required.
  8. [![Release](https://img.shields.io/github/v/release/rekal-dev/rekal-cli?color=22d3ee)](https://github.com/rekal-dev/rekal-cli/releases)
  9. [![CI](https://img.shields.io/github/actions/workflow/status/rekal-dev/rekal-cli/ci.yml?branch=main&label=ci)](https://github.com/rekal-dev/rekal-cli/actions/workflows/ci.yml)
  10. [![License](https://img.shields.io/github/license/rekal-dev/rekal-cli?color=blue)](LICENSE)
  11. [Get started](#quick-start) · [Documentation](#documentation) · [Website](https://rekal.dev)
  12. ## Get context. Then get to work.
  13. [![Illustrative conversations: Alex builds invoice exports with Claude Code; Sam uses that context in Codex to add date filters](docs/assets/demo.gif)](https://rekal.dev/#demo)
  14. Your agent finds relevant context from your team and past work, reads the
  15. sources and uses what matters for the job.
  16. **Agents own the reasoning. Rekal makes the context durable, retrievable and shared.**
  17. As agents improve at memory and distillation, they can do more with the project
  18. record you already have. [Core principles](SOUL.md#the-core-bet-enable-the-agent).
  19. Works with **Claude Code, Cursor, Copilot, Codex, Gemini, Kiro and OpenCode**.
  20. Claude project notes are captured by default; other note sources are configurable.
  21. ## Quick start
  22. ### From a shell
  23. ```bash
  24. curl -fsSL https://rekal.dev/install.sh | bash
  25. export PATH="$HOME/.local/bin:$PATH"
  26. rekal version
  27. cd your-project
  28. rekal init
  29. ```
  30. The installer gets the **latest release** and verifies its checksum.
  31. Supports macOS ARM64, Linux AMD64 and Linux ARM64.
  32. The PATH line is for Bash/Zsh; in Fish, use `fish_add_path "$HOME/.local/bin"`.
  33. Work with your agent, then commit normally to capture the context.
  34. Already have local sessions? After first `rekal init`, your agent will be able to search context in your past conversations history across local memories and other seissions from other agent types. For shared team history,
  35. run `rekal sync`, then ask your agent to rekal team context or specific team member's context.
  36. [Setup and sharing details](docs/overview.md) · [Privacy and security](SECURITY.md)
  37. ## Documentation
  38. - [Using Rekal](docs/usage.md) — setup, capture and team workflows
  39. - [Search and memory](docs/overview.md) — source reads, native notes and sharing
  40. - [Commands](docs/commands.md) · [Configuration](docs/configuration.md)
  41. - [Design principles](SOUL.md) · [Benchmarks](docs/research/benchmarks.md)
  42. - [Development](docs/DEVELOPMENT.md) · [Contributing](CONTRIBUTING.md)
  43. [Get help](https://github.com/rekal-dev/rekal-cli/issues) ·
  44. [Changelog](CHANGELOG.md) · [Paper and citation](docs/overview.md#citation)
  45. [![Website](https://img.shields.io/badge/website-rekal.dev-0ea5e9)](https://rekal.dev)
  46. [![Downloads](https://img.shields.io/endpoint?url=https%3A%2F%2Frekal.dev%2Fdownloads.json)](https://rekal.dev/#downloads)
  47. [![arXiv](https://img.shields.io/badge/arXiv-2607.14390-b31b1b)](https://arxiv.org/abs/2607.14390)
  48. [![Discord](https://img.shields.io/badge/Discord-join-5865F2?logo=discord&logoColor=white)](https://discord.gg/hDMj8zHH2)
  49. [![Stars](https://img.shields.io/github/stars/rekal-dev/rekal-cli?style=social)](https://github.com/rekal-dev/rekal-cli/stargazers)
  50. Apache-2.0 — see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.