Introducing a Managed Plan Exclusive Feature: Memory
Most AI commands meet you for the first time every time.
They can follow an instruction, but they do not remember the names you use, the tone you prefer, or what worked in the last execution. That missing history is why a rewrite can feel right today and strangely generic tomorrow.
Memory changes that. It is a new feature for Echoo Pro and Max that gives each command access to its active execution history, so every run starts with more context than the one before it.
Better command executions, built from real history
Turn on Memory for a command and Echoo keeps that command in an ongoing conversation with the AI provider. The provider can see the command's earlier requests and results instead of handling each execution as an isolated prompt.
This is not a profile you have to configure. It is the command's real working history.
That history helps the provider recognize the details that make your writing yours: company and product names, recurring terminology, sentence length, level of formality, and how much detail you usually keep. A Rewrite command that has handled fifty of your messages has better context than one running for the first time.
The result is not simply a longer prompt. It is a command that can make better decisions because it knows what happened before.
A managed-plan exclusive
Memory is available on Pro and Max because reliable command history requires a managed connection between Echoo and the AI provider.
Free mode remains BYOK: you choose a cloud or local provider and use your own key. That freedom is useful, but providers handle conversation history differently. Echoo cannot promise the same persistent Memory experience across every BYOK setup.
The managed plan gives Echoo one consistent way to maintain command history while preserving the freedom to improve or change the underlying model over time. You get the feature, not a dependency on one model name.
Privacy without another personal profile
Memory uses the conversation capability already provided by the AI service behind the managed plan. Echoo does not need to build a separate personal profile from your writing or duplicate your history into another personalization system.
Your command still runs with the AI provider, as it did before. Memory simply lets that provider use the command's existing conversation history when producing the next result.
This keeps the design focused: better context for the command, without turning all of your Echoo activity into one global identity.
One memory per command
Memory is controlled separately for each command in Settings, right below Screen Context.
That separation matters. What Rewrite learns should not affect Translate. A command for concise client emails should not shape a command that expands meeting notes. Each command keeps only the history relevant to its own job.
Enable it where repeated context improves the result. Leave it off where every execution should start clean.
Full history, with a practical limit
Within its active conversation, the provider receives the command's execution history rather than a guessed summary of your preferences. But history has a cost: as a conversation grows, each execution requires more context to process.
To keep Memory responsive and credits predictable, Echoo limits how large an active conversation can become. When it reaches that limit, the command starts a fresh conversation and begins learning again.
You can also reset a command's Memory at any time. That is useful when a role, client, writing style, or workflow changes—or when one unhelpful result should not become the example for the next one.
Memory ships in Echoo 1.1.0 for Pro and Max. Enable it for one command and let the next execution start where the last one finished.
Mike
Creator of Echoo