Security in every review: Semgrep runs before the model reads a line See how

Memory

Everything that happened, in one record.

See what changed in your code, who changed it and why, across pull requests, reviews and pushes on GitHub.

Free for 250 events a month. Unlimited seats. Your own model keys.

Problem

The pull request merged. The reason left with it.

Months later, nobody remembers why a change was made or who agreed to it. Memory keeps that trail in one place.

How

From the first signal to the next action.

  1. 01

    Connect

    Install the GitHub app. Pull requests, reviews and pushes arrive as events.

  2. 02

    Record

    Each event is kept with when it happened, who was involved, why and how it went.

  3. 03

    Recall

    Open the record when you need the history behind a change.

Docs

History you can check.

Every entry names its source, its time and the people involved. Memory is an add-on to code review.

Read the memory documentation

FAQ

Before you get started.

Which sources are live?

GitHub: pull requests, reviews and pushes. Slack threads, meetings and coding sessions are planned.

How is Memory different from Knowledge?

Knowledge is what your team holds true: decisions, conventions and constraints. Memory is what happened: the events that led to it.

Is Memory part of every plan?

No. Memory is an add-on to code review.

SourceAnt · Memory

Everything that happened, in one record.