mevebu / memogit
Latest version v0.2.1

Memory for coding agents, one note at a time.

memogit gives your agent a local folder, .memogit, where it writes one dated note after each real session. The next session reads the newest notes and continues with context instead of starting from zero.

npx memogit

Run it inside your project folder. It creates the folder and adds it to .gitignore.

Open on GitHub See how notes look

The problem

Every session starts from zero.

"We already fixed this last week." "The API returns 500, not 401, remember?" "The next step was the migration, not the UI." The work you did yesterday is in a chat window that is now closed.

memogit writes it down in a shape both a human and an agent can scan, and keeps it out of git.

.memogit/

2026-10-20 03.51.46.md
2026-10-19 16.08.02.md
2026-10-18 09.22.11.md

One dated note per session. The folder stays out of git.

You repeat the same context every session.

The agent reopens a decision you already settled.

The next step is lost between sessions.

What gets written

One note per session, in a fixed shape.

Each note is small on purpose: under 120 lines, six sections, at most five bullets each. Short enough for an agent to read three of them before starting.

memogit skill

Writes one dated markdown note after each meaningful session, in YYYY-MM-DD HH.mm.ss.md inside .memogit/.

.memogit/2026-10-20 03.51.46.md 
---
created: 2026-10-20T03:51:46+07:00
project: example-app
branch: main
agent: kilo
status: done
tags: [auth, api]
---

# 2026-10-20 03.51.46

## Goal
Add a session refresh path so a logged in user stays signed in.

## Changed
- `src/auth/session.ts`: added `refreshSession()` and a single retry on a 401.

## Decisions
- Kept the call inside the existing client instead of a second HTTP layer.
- Rejected a background timer because the app can be idle for hours.

## Verified
- `npm test -- session` passed. Browser flow not run, so still unverified.

## Problems
- Staging returns 500 instead of 401 for an expired token.

## Next
- Confirm with the backend owner, then drop the 500 fallback.

Install

Interactive, silent, or global.

Run it in the project folder. It asks where to install and which editors you use, then creates the folder and the rule file.

Interactive installer

terminal 
npx memogit

Non-interactive

terminal 
npx memogit --yes

Every project on this machine

terminal 
npx memogit --yes --global

Use the skills CLI if you install skills through skills.sh.

npx skills add mevebu/memogit --all

How it works

Write, then read. That is the whole loop.

  1. Install once per project

    The installer copies the skill, writes a rule file, and creates .memogit/.

  2. Work as usual

    After a meaningful session, the agent writes one dated note with what changed, what was decided, and what comes next.

  3. Start with context

    The next session reads at most three recent notes, then continues where the last one stopped.

FAQ

Common questions.

Does the .memogit folder get committed?

No. The installer adds it to .gitignore. It is working memory, not a deliverable.

How long is each note?

Under 120 lines, in six sections with at most five bullets each. The limits are what keep it readable.

Can two people on a team use it?

Yes. Each person keeps their own local notes. If notes should be shared, commit them deliberately instead of relying on the folder.

Does it store secrets?

The rules tell the agent to keep secrets and personal data out of the notes. Since the folder is local, a mistake stays local too.

Stop re-explaining your project.

One install per project, and the context carries forward.

npx memogit
Read the README

Also from mevebu

Continue to the rest of the set.

mevebu

230 browser tools for the small jobs. Private by default, one page each.

waitsec

Guardrails that keep the agent focused, honest, and inside the change you asked for.