In partnership with
Dictate code. Ship faster.
Wispr Flow understands code syntax, technical terms, and developer jargon. Say async/await, useEffect, or try/catch and get exactly what you said. No hallucinated syntax. No broken logic.
Flow works system-wide in Cursor, VS Code, Windsurf, and every IDE. Dictate code comments, write documentation, create PRs, and give coding agents detailed context- all by talking instead of typing.
89% of messages sent with zero edits. 4x faster than typing. Millions of developers use Flow worldwide, including teams at OpenAI, Vercel, and Clay.
Available on Mac, Windows, iPhone, and now Android - free and unlimited on Android during launch.
Many AI coding tools have always had one frustrating flaw: they forget everything the moment a session ends.
Claude Code’s new auto-memory feature changes that by letting the assistant retain useful project knowledge between sessions, turning it from a stateless helper into something closer to a long-term collaborator.
Instead of constantly re-explaining your setup, conventions, and debugging lessons, Claude can now carry that context forward automatically.
The result is a workflow that feels less like starting over every time—and more like picking up exactly where you left off.
How it works
Passive capture
Auto-memory runs quietly in the background.
As you work, Claude identifies recurring patterns, debugging insights, and workflow preferences, then stores them in a local markdown memory file.
Over time it begins capturing things like:
how your team runs tests
which package manager the repo uses
conventions for naming services or components
recurring debugging lessons
local environment quirks
Instead of manually documenting every small lesson, Claude gradually builds a lightweight project memory as you work.
This is important because most of these details are never formally documented—they’re just things developers repeat in every AI session.
Automatic injection
The real value appears when you start a new session.
Claude immediately reads the project memory file, which effectively warms up its context before any interaction begins.
This means Claude can start with awareness of things like:
your preferred test command
project tooling choices
known debugging pitfalls
team conventions
Instead of:
rescanning large files to rediscover patterns
asking you the same setup questions
requiring repeated explanations
The memory acts like a compact summary of the project’s operational knowledge.
User control
Persistent memory only works if developers can control it.
Claude provides a /memory command that lets you:
review saved memory
edit stored information
delete outdated entries
disable auto-memory if needed
This matters because project reality changes. For example:
a workaround might become obsolete after a refactor
a naming convention may evolve
debugging notes may no longer apply
With direct access to the stored markdown, you can prune outdated knowledge and keep the memory accurate.
Why it matters
1. Zero-day productivity
The biggest improvement is eliminating session amnesia.
Without persistent memory, every new session often starts with explanations like:
how to run the test suite
how the repo is structured
which framework conventions your team follows
Auto-memory removes most of that overhead.
Each new session begins closer to a continuation than a restart, which means less setup and faster time to useful work.
See Why HubSpot Chose Mintlify for Docs
HubSpot switched to Mintlify and saw 3x faster builds with 50% fewer eng resources. Beautiful, AI-native documentation that scales with your product — no custom infrastructure required.