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 · each verdict is earned from what beta tenants actually stopped opening.

what 3ngram replaces · the quiet victories
notion running docs · meeting notes
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.
beta users kept: wiki pages, RFCs
beta users stopped opening: project running-docs
replaces ✓
CLAUDE.md per-repo context files
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.
imports your existing CLAUDE.md on first connect
kept in sync: automatic
replaces ✓
mem0 flat AI memory store
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.
migration: one click · 4 min
see: switch to 3ngram
replaces ✓
post-its · sticky notes the analog backup
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 catches it — and reaches you on telegram when the window opens.
the commitment is captured the moment you mention it
the sticky becomes redundant
replaces ✓
what 3ngram reduces · these get quieter, not deleted
linear issue tracker
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.
personal reminders: drift into 3ngram
team issues: unchanged
reduces ↓
todoist · things · reminders personal to-do apps
manual to-do entry shrinks. what survives is the stuff 3ngram can't overhear — groceries, picking up dry cleaning, things outside your AI conversations.
survives: errands, household
subsumed: work commitments
reduces ↓
meeting recap emails the "per our conversation" follow-up
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.
drafted: auto · you sign off
reduces ↓
what 3ngram leaves alone · the tools we stay out of
claude · chatgpt your AI assistant
3ngram sits behind these, not in front of them. you keep drafting in Claude. you keep exploring in ChatGPT. we only save what you tell the agent to save.
connection: MCP server
capture: only when you ask the agent to debrief
untouched
cursor · codex AI coding agents
you keep writing code in Cursor. 3ngram captures the decisions and commitments from your agent sessions. we don't touch the code.
permissions: read-only on chat + commits
untouched
gmail · slack comms (roadmap)
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.
status: roadmap · no capture today
untouched
google calendar events + agendas
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.
read: calendars you grant
write: sign-off required
untouched

we don't want a place in your stack. we want a layer behind it.

get started free ↵