per-repo context filesreplaces ✓
CLAUDE.md
the hand-maintained context file that tries to prime every new Claude session — stack, conventions, open decisions — becomes automatic. 3ngram writes it, updates it, and exposes it via MCP.
replaces ·the tools 3ngram quiets — and the ones it doesn't
3ngram doesn't swap for your AI. it swaps for the layer around it.
the docs, the tickets, the post-its. three verdicts — replaces, reduces, leaves alone — and each verdict is earned from what early users actually stopped opening.
verdict ·the quiet victories
what 3ngram replaces.
running docs · meeting notesreplaces ✓
notion
the "running doc" for a project — the one that becomes a dumping ground for decisions, deadlines, and post-meeting TODOs — stops getting opened. 3ngram captures the same content in place, from the conversation that generated it.
the full breakdown →
flat AI memory storereplaces ✓
mem0
a flat memory store remembers "user prefers brevity". 3ngram remembers commitments with deadlines and decisions with rationale. If you were using Mem0 as a notebook, 3ngram subsumes it.
the full breakdown →
the analog backupreplaces ✓
post-its · sticky notes
the sticky on your monitor that says "reply to Camilla re: salary band" is an admission that your software didn't catch the commitment. 3ngram keeps it available for briefings and search.
verdict ·these get quieter, not deleted
what 3ngram reduces.
issue trackerreduces ↓
linear
you still use Linear for engineering triage. but the informal tickets you open on yourself — "remember to bump the version" — stop happening. those land in 3ngram commitments.
the full breakdown →
personal to-do appsreduces ↓
todoist · things · reminders
manual to-do entry shrinks. what survives is the stuff 3ngram can't overhear — groceries, picking up dry cleaning, things outside your AI conversations.
the full breakdown →
the "per our conversation" follow-upreduces ↓
meeting recap emails
the email you write after every call to recap who agreed to what — 3ngram drafts it from the transcript and the commitments it pulled. you approve and send.
the full breakdown →
verdict ·the tools we stay out of
what 3ngram leaves alone.
your AI assistantuntouched
claude · chatgpt
3ngram sits behind these, not in front of them. you keep drafting in Claude. you keep exploring in ChatGPT. your assistant remembers what matters as you work.
AI coding agentsuntouched
cursor · codex
you keep writing code in Cursor. 3ngram captures the decisions and commitments from your agent sessions. we don't touch the code.
comms (roadmap)untouched
gmail · slack
gmail and slack integrations are on the roadmap. when they ship, we'll only read what you opt into — outbound for gmail, channel-by-channel for slack — and we'll never send without your sign-off.
events + agendasuntouched
google calendar
3ngram reads the calendars you grant for context — when you're in a call, when a commitment lands. event writes happen only with explicit approval.