Feature deep-dive

Teach Navi once, never re-explain

The single biggest difference between using Navi on day one and using it on day thirty is memory. Here's what it does and how to use it well.

Need help? Join the Navi community on Discord, r/naviwork, or the Facebook group — that's the fastest way to get answers.

Everyone starts a new ChatGPT conversation the same way: "Let me explain what I do, who my team is, how I like emails written, what projects I'm on…" Then the conversation ends and tomorrow you do it again.

Navi has a feature called long-term memory. Tell it something about you, your work, or your preferences, and it remembers — across every chat, forever, until you change it. The next time Navi needs that context, it just has it.

What lives in memory

Three kinds of things are worth teaching Navi once:

Who's who. The people in your professional life. Their names, titles, teams, relationships to you. Who you report to. Who reports to you. Who your key external contacts are.

How you like things done. Your voice. Your signoff. Your scheduling preferences. Which days are off-limits for meetings. Which channels or databases to use for what.

What projects are live. What you're working on. What matters this quarter. What's blocked. The code names or nicknames your team uses.

Teaching Navi: the magic word

There's no special interface. Just say "remember." Navi will file it:

Prompt Remember: my team is Sarah Chen (CTO), Dan Orozco (Head of Sales), and Priya Patel (Product). My manager is Alex. My main Linear projects are Checkout, Search, and Growth. My calendar rules: no meetings before 9am or after 5pm Pacific, no meetings Friday afternoons, and Tuesday/Thursday mornings are blocked for deep work.

From that moment on, every interaction has that context. When you ask "block time for me to do the quarterly review," Navi will know to avoid your deep-work blocks. When you ask "summarize what's going on in Checkout," it'll know which Linear project to look at.

Good memory prompts

A few patterns that pay off:

Voice Remember my writing voice: short sentences. Lowercase when messaging my own team. Full sentences and capitalized sign-off ("Thanks, M.") when writing to customers or investors.
VIPs Remember: always flag anything from these people as urgent — Alex (my manager), Jordan (our board lead), Sarah (my CTO), and anyone from @acme.com (our largest customer).
Tool shortcuts Remember my workspace layout: meeting notes go in the "Meeting Notes" Notion database, customer deals in "Pipeline," weekly reviews in "Weekly reviews." Personal to-dos live on a Notion page called "Next up."
Ongoing context Remember: we are preparing a Series B pitch for Q3. The target is a $20M round at a $120M pre. Lead candidate is Sequoia. Current status is: first meeting done, deck in revision, data room half-built. Flag anything fundraising-related as high priority.

When memory pays off most

Memory shines in scheduled agents. Imagine you've taught Navi your voice, your VIPs, and your preferred doc layout. Now when your morning calendar briefing or weekly Linear roll-up runs, the summary is already in your voice, already flags the right people, already formatted the way you like. You don't re-configure. You set up the agent once and it inherits everything.

Same with recurring drafts. Your weekly team update in the voice you'd use naturally. Your meeting agendas formatted like yours. Your project recaps shaped the way you think.

Keeping memory clean

Memories aren't permanent if you don't want them to be. A few maintenance prompts:

Prompt What do you remember about me? Summarize my long-term memory.
Prompt Forget that I was working on the Series B. We closed it. Instead remember: current focus is hiring a VP Sales and shipping the v2 platform.
Prompt Remove anything outdated from memory — anything describing projects or people that no longer apply.

Why this matters

Most AI tools feel like they reset every time you open them. Navi feels like it knows you. That's not magic; it's just memory used deliberately. Spend ten minutes teaching Navi the fundamentals this week, and every interaction from then on is better.

More on the core ideas in what is Navi, and how it shows up in automation in the scheduled agents guide.

Questions? Stuck? Want to share something you built?

Come join the Navi community — the fastest way to get help or compare notes with other users:

← All posts