three verdicts: replaces · reduces · leaves alone · v1 capture is explicit; source-system connectors and outbound agents are not shipped.
a hand-maintained file that only exists to remind the next AI session what happened can become typed memory instead. you choose what to save, and the original long-form docs stay where they are.
the full breakdown →
if you used a generic memory API as a personal notebook, 3ngram adds typed decisions, commitment status, revision lineage, briefings, and a hosted user experience. there is no automatic importer in v1.
the full breakdown →
the sticky on your monitor that says "reply to Camilla re: salary band" is an admission that your software didn't retain the commitment. Ask the agent to save it, and 3ngram brings it back in a later briefing.
you still use Linear for engineering triage. informal AI-work reminders can live as 3ngram commitments when you explicitly save them, while team issues stay in the tracker.
the full breakdown →
you can explicitly save commitments that arise in an AI session. 3ngram does not overhear conversations, send reminders, or replace a general-purpose task manager.
the full breakdown →
after you explicitly save meeting outcomes, an AI client can search those memories and draft a recap when you ask. 3ngram does not ingest the transcript or send the email.
the full breakdown →
keep CLAUDE.md for static repository instructions. use 3ngram for decisions, blockers, and commitments you explicitly save and want available outside Claude or one repository.
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.
you keep writing code in Cursor or Codex. 3ngram stores only memories the client explicitly writes; it has no repository, commit, or passive chat access in v1.
gmail and slack integrations are not part of v1. 3ngram does not read, post, or send through either service.
Google Calendar sync is not part of v1. Today you can explicitly save a meeting commitment or agenda fact through an MCP client; automatic calendar reads and writes remain roadmap work.