How it worksFeaturesRecallPricingFAQ Install free
v2.4Works with VS Code, JetBrains & Neovim

Your codebase remembers, so you don't have to.

ByteMemo captures the decisions, snippets and context behind your code — then recalls them in your editor with a single keystroke. Stop asking "why is it like this?" in the team channel.

$npm i -g bytememo
1 keystroketo recall
30ssetup
Local-firstby default
4.9★dev rating
auth/session.tsbytememo
1// the cache we use for sessions…
2export async function getSession(id: string) {
3 return cache.get(`sess:${id}`) ?? db.load(id);
4}
5
6// …but wait, why not Redis here?
⌘Kwhy did we drop redis?
✓Moved to in-process LRU cachedecided by A. Rivera · PR #412 · 3 months ago
↩Redis added 2.1ms p50 latency on readsfrom benchmark.md · linked to #388
💬"Single region, single node — cache it locally."thread · #architecture · 12 replies
Captures context from GitHubLinearSlackNotionJiraConfluence
How it works

It watches, it remembers, it answers.

ByteMemo quietly reads the context around your code — commits, PRs, tickets, threads — and turns it into a searchable memory you can ask questions.

01 · capture

It reads the trail

Commits, PR descriptions, review comments, linked tickets and design docs are ingested and indexed against the files they touch.

// PR #412 → auth/session.ts
02 · link

It connects the dots

Decisions get attached to the exact lines they explain, so the "why" travels with the code instead of living in someone's head.

// 3 memories linked to this file
03 · recall

You just ask

Hit ⌘K in your editor and ask in plain English. You get the answer, the source and the person — no tab-switching archaeology.

> why no redis here?
Features

Built for the way engineers actually work.

⌘

Recall inside your editor

One keystroke opens a palette you already know the shape of. Ask a question, get a cited answer without leaving the file you're in.

⌘K "why is this retried 3 times?"
→ added for the flaky payments API · PR #588
🔒

Local-first, private by default

Your code never has to leave your machine. Run the index locally, sync only what you choose, and audit exactly what's stored.

🧠

Zero-effort memory

It captures context automatically. No notes to write, no ritual to keep.

🔗

Every answer cited

Each recall links to the PR, ticket or comment it came from.

👥

Team-shared

When someone leaves, the knowledge stays with the code.

Try it live

Ask your codebase a question.

Type below to search a sample team memory. The real thing indexes your own repos — this is just a taste.

⌕⌘K
Proven in real teams

Less archaeology, more shipping.

"Onboarding used to mean pinging three seniors for a week. New hires now ask ByteMemo first — and get a cited answer in seconds."
EL
Emma L.Eng manager · 40-person team
"It answers the 'why is it like this?' questions that no comment ever captures. I've stopped being a human git blame."
RS
Rahul S.Staff engineer
"Local-first sold it for us. Index runs on the laptop, nothing sensitive leaves the building, and it still works with Slack and Linear."
MW
Maya W.Platform lead · fintech
Pricing

Free to remember. Pay to share.

Solo

For one developer, one machine.
£0/forever
  • ✓Local index, unlimited repos
  • ✓Editor recall (⌘K)
  • ✓Git + PR context
  • ✓Export everything, anytime
Install free
For teams

Team

Shared memory across the whole org.
£12 /seat /mo
  • ✓Everything in Solo
  • ✓Team-shared memory
  • ✓Slack, Linear & Jira ingest
  • ✓Self-host or cloud
  • ✓SSO & audit log
Start 14-day trial
FAQ

Good questions.

Does my code leave my machine?

Not by default. ByteMemo runs the index locally and works offline. Team sync is opt-in and scoped — you choose exactly what's shared, and there's a full audit log of what's stored.

Which editors are supported?

VS Code and Cursor first-class, plus a JetBrains plugin and a Neovim extension. All of them use the same ⌘K recall, so muscle memory carries over.

What does it actually read?

Git history and PR descriptions/reviews, plus linked tickets and threads from Linear, Jira, Slack and Notion if you connect them. It maps all of it to the files and lines it explains.

How accurate are the answers?

Every recall cites its source — the PR, ticket or comment — so you can verify in one click. It's designed to show its work, not to bluff.

Can we self-host?

Yes. The Team plan supports self-hosting the index and sync server inside your own infrastructure, so nothing sensitive ever touches our cloud.

Give your codebase a memory.

Install in 30 seconds, free for solo developers. Your future self — and every new hire — will thank you.