EVO CAPABILITIES / Persistent work and project state
Pick up the work, with its decisions intact.
A persistent AI workspace connects your goal, selected sources, decisions and recorded results, so returning to a project starts with what matters next.
Mac development · See current scopeThe real problem
A project rarely ends when a chat does. A founder may leave with a revised product brief, a website issue still under review and a decision waiting on a colleague. Three days later, the difficult part is reconstructing which version mattered, what was actually changed and what still needs checking. A useful restart should preserve those distinctions, rather than ask you to explain the project from the beginning.
What chat history leaves you to do
A transcript records what people said in order. By itself, it does not establish that a promised edit happened, that an old source remains current or that a test satisfied the goal. Other AI products can add project features too; the useful comparison is whether the work has an inspectable state beyond the latest answer.
How EVO approaches it
Keep the goal beside the evidence
EVO keeps a saved Work with its requirements, chosen files, research sources, decisions and supported action results. The conversation explains the work; the recorded outcome tells you what happened. Proposed, applied, pending and unverified items remain different, so a confident reply cannot turn an unfinished task into an accepted result.
Bring forward relevant, usable context
When you review a continuation, EVO selects a limited set of still-valid prior tool results and current application outcomes from that work. It checks them against the sources and access you choose now. This is targeted continuity, not a claim that every old conversation is searched or that every historical word fits into the next answer.
Recheck what time or change can invalidate
A changed document, an obsolete application result or a revoked choice should not quietly become today's evidence. Previous web and current-time observations need a fresh observation before reuse in the supported continuation path. The review shows where context is missing or no longer usable, letting you decide what to refresh.
Resume from a reviewed stopping point
Reviewing a checkpoint prepares the next request without executing it. You can adjust the goal, inspect outstanding decisions and send when ready. New work uses the permissions for that request; old approval does not become a permanent licence to repeat a consequential action.
A concrete example
ILLUSTRATIVE WORKFLOW · NOT A CUSTOMER RESULT
Illustrative workflow: return to a website improvement
A founder has reviewed a product page, applied one selected file change and left mobile validation open. On returning, the question is: what still stands between this revision and acceptance?
Open the same Work and review the saved goal, selected revision and actual results.
Keep the completed change distinct from the mobile check that has not been performed.
Refresh the relevant page evidence, then choose the next check or revision.
What you take away
The intended deliverable is a continuation brief: what changed, which evidence supports it, what remains unverified and the next meaningful action. You can focus on the open check instead of manually reconstructing the previous session.
Your choices
- Choose the work and sources to carry forward; edit the next request before sending.
- Inspect recorded outcomes and keep uncertain or incomplete checks visible.
- Stop a run, change its scope or withhold a new action approval without erasing the saved project.
Current scope
Implemented foundation
- Selected conversations, file references and operation results survived an isolated restart check on 15 September 2026.
- That check did not qualify a complete project handoff. A later local answer guessed an unselected source; this remains an open issue.
Next milestones
- Public Alpha access and unattended continuation are not released. Broad retrieval across all historical conversations and automatic cross-device handoff are separate work.
- A saved checkpoint cannot refresh every external fact or prove every goal is met. Important deliverables still need the relevant verification and your review.
These are development capabilities, not a public release. See platform availability before requesting a trial.
Platforms and availabilityRelated questions
Which project state does EVO keep for a return visit?
EVO can keep the saved goal, constraints, recent discussion, available evidence, action history and remaining verification around a Work.
Reviewed continuation can reuse selected previous tool results and current saved action outcomes, while excluding changed or unavailable sources.
After a website edit, return to the applied change and see that a mobile preview still needs checking, instead of assuming the entire task is finished.
Inspect the checkpoint and choose what belongs in the next run; you can change the goal or supply updated material.
The stored state covers supported, recorded activity. It is not a live model of every app, file or event in your life.
How does EVO find relevant context in a long history?
EVO uses limited recent conversation, the selected Work and approved memory selected for the task, rather than sending the entire archive on every request.
Supported search looks within material already available to the current task. A reviewed continuation can add relevant prior results with their sources.
To revisit a requirement from an older project, reopen that Work or provide the relevant excerpt instead of expecting every old message to be present.
Select the project, correct a missing reference and review what context is being used.
Universal semantic search across all conversations is not a qualified capability. Relevance can be missed, and a long saved history does not mean unlimited model context.
How does EVO decide whether a task is finished?
EVO separates producing an answer from meeting the Work’s agreed success conditions, so remaining checks can stay visible after a response ends.
Where supported, completion review connects the requested outcome to actual evidence and asks you to inspect unresolved limits before accepting it.
A supplier shortlist may be written while one important source still needs confirmation; a website file may be saved while its mobile behavior remains unchecked.
Define the result you need, review the evidence and decide whether the remaining limitations are acceptable.
Not every task has an automatic outcome check. Real-world effects and subjective quality can still require your judgment or additional testing.
How does EVO handle information that may be out of date?
EVO keeps source timing and saved state distinct from present-day truth, and reviewed continuation excludes certain changed or time-sensitive results until they are checked again.
A previous web observation is not automatically a fresh observation. A changed selected file or application result can invalidate its earlier context.
Returning to a price comparison should trigger new source checking rather than treating last week’s price as today’s.
Provide updated material, review source dates and explicitly continue the checks you need.
A capture date does not establish when the publisher updated a page. EVO does not continuously refresh all saved information in the background.
Do I need to approve everything again when I continue?
Reopening saved work does not itself run an action. A new run uses the permissions and selected material valid for that continuation.
Some eligible permissions may be reusable; changed sources, cloud sharing and consequential actions have their own renewed review requirements.
You can inspect a previous result without rerunning it, then choose the next check and review any new action it proposes.
Review the continuation, edit the next request and send when ready. You can revoke reusable permissions.
An old approval is not unlimited future authority. Stop does not reverse completed effects, and uncertain outcomes may need reconciliation before retrying.
Try the workflow
Bring 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.