MemophantMemophant
Who it's for

For everyone who's tired of re-explaining the repo.

If your AI assistant starts every session from zero — re-learning the architecture, re-asking the same questions, forgetting yesterday's decision — repo-resident memory fixes it. Here's what that looks like for the way you work.

Solo developers

Your assistant, as caught-up as you are.

Stop re-onboarding your agent every morning. Your decisions, conventions, and the gotchas you hit last week wait in the repo, so the next session opens already knowing how your project works — and why.

  • One-time purchase, yours forever — no subscription; one license per person
  • No team setup, no cloud account — it's your Mac and your repo
  • Capture a decision the moment you make it; query it for months
  • Switch between Claude Code, Cursor, Codex, or Gemini without re-priming
A Memophant project open beside an editor, the agent reading memory at session start.
A pull request diff of a .memory/ note, with the provenance row and a reviewer comment.

Teams

End the divergent-agent problem.

When everyone's sessions write to private scratchpads, parallel agents fork contradictory assumptions. Point them at one shared, reviewable memory instead — and let drift get flagged before anyone acts on a stale fact.

  • Plain-markdown memory, reviewed in normal pull requests
  • Provenance on every note — who decided what, against which commit
  • One source of truth every teammate's agent reads first
  • Stale notes surface on the dashboard before they mislead
  • Licensed one seat per person — each teammate buys their own

Agencies & consultants

Hand off a project with its memory intact.

Spin up per-client repos that already know their conventions, their credentials, and their setup steps. When the engagement ends, the knowledge stays with the repo instead of walking out the door in someone's head.

  • Per-repo registry on your Mac — every client kept separate
  • Portable: memory is just files, so a handoff is a git clone
  • Vendor registry keeps client credentials in the Keychain, not chat
  • Templates turn repeated client setups into a one-command kit
The project sidebar listing several client repos, each with its own memory and vendor registry.

However you work, the next session shouldn't start from zero.

Repo-resident memory that fits a solo dev, a team, or a roster of clients.