Change what EVO knows when your work changes.
Keep useful preferences available across conversations, without letting an old assumption become a permanent instruction.
In the Mac preview · Illustrative workflow · Not a customer testimonial or a measured end-to-end result.
The starting point
A designer previously asked for short client-facing answers. Their new project needs detailed technical explanations. They want EVO to retain the useful preference in the right context, correct what no longer applies and avoid repeating the same correction every day.
A preference buried in a transcript is hard to inspect. Treating every remark as a permanent rule causes the opposite problem: a temporary deadline or one unusual request can shape later answers long after its purpose has passed.
What you bring
- The current request and the memory entry the user wants to examine.
- An explicit instruction to remember, correct or stop using a particular item.
- The distinction between a project-specific requirement and a preference intended for future conversations.
What EVO needs to understand
EVO separates the present task from approved shared memory. A memory change is a proposal to review, not an automatic conclusion from a passing comment. Current explicit instructions remain important even when an older preference is available.
Working through it
See the actual remembered item
Open Memory to inspect the saved entry. Loading, unavailable information and a confirmed empty collection are shown differently, so a failed read cannot falsely reassure you that nothing is remembered.
Describe the correction
Prepare a request such as keeping concise client messages while allowing detailed engineering explanations for this project. The request enters an unsent conversation draft without discarding text already there. You can revise it before sending.
Approve the useful change
Review the specific memory proposal and its intended future use. Once approved, eligible memory can inform later conversations within their context limits. If an item is forgotten, it stops entering future context through that memory path.
What you receive
- A visible, reviewable memory item instead of an assumption hidden in chat history.
- An explicit proposal to add or forget information, with its decision recorded.
- A clearer boundary between today's instructions and what should remain useful later.
When you come back
The approved preference can be selected for subsequent work; it is not necessary to paste it into every new conversation. Review it again when your circumstances change. A backup restoration requires fresh consent before restored memories are reused.
Your information and choices
- Inspect memory and ask EVO to propose a reasonable addition or removal.
- Approve future sharing separately from drafting the request.
- Keep reference documents in their own collection rather than treating them as personal facts.
Current scope
Implemented foundation
- Memory viewing, reviewed remember/forget requests and guarded reuse exist in the Mac development build.
Next milestones
- Forgetting suppresses future memory use; it does not erase every conversation, approval record or external backup.
- The example describes intended use of the implemented controls, not a measured guarantee that a model will follow every preference perfectly.
These are development capabilities, not a public release. See platform availability before requesting a trial.
Platforms and availabilityBring a task you want to move forward.
Explore the Mac release, or tell us which workflow you would like to evaluate. An application does not guarantee an invitation.