Review what is worth remembering.
Save a useful preference deliberately, and change it when your work changes.
Internal workflow illustration · Not publicly available or an end-to-end qualification.
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 useful preference should last beyond this chat, without turning every casual comment into a permanent memory.
What you bring
- One explicit preference to save, or one existing memory to correct.
A request to start with
Remember: the first EVO release does not include a full iPhone app.
Internal Mac development workflow; no public plan is offered. Requires a compatible downloaded local model or an eligible online cloud route; review selected content before sending it to the cloud.
What EVO needs to understand
Prepare a memory suggestion, then wait for confirmation.
Working through it
Make the request explicit
Ask to remember the preference. The local test created one pending suggestion and zero confirmed memories.
Review before saving
Check the wording, correct it or decline. Pending approval is not saved memory.
Manage later changes
In supported internal flows, inspect the saved item and request a correction or deletion. A deletion must finish before EVO can say it has forgotten the item.
What you receive
- A memory suggestion you can inspect.
- A saved preference only after the supported approval flow completes.
First release: Mac first Awaiting your confirmation
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
- The pending-memory boundary was tested with real local Swift on Mac.
- Internal App only. No public plan or complete memory-management GUI qualification is claimed.
Next milestones
- Consistent recall, correction, deletion and complete App interaction still need joint qualification.
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.