EVO CAPABILITIES / Computer tools and browser inspection
Move from advice to work you can inspect.
EVO combines selected local tools, supported app operations and rendered browser evidence, with a clear difference between proposing an action and completing it.
Mac development · See current scopeThe real problem
A useful assistant should help close the gap between a recommendation and the work it creates. After planning a week, you still need tasks. After reviewing a website, you still need to see the actual page and check the change. The challenge is to make those steps accessible while keeping you informed about exactly what was read, changed or left unfinished.
What chat history leaves you to do
A text answer can tell you how to do something without performing it. A tool-enabled assistant can go further, but the presence of a button or a successful tool response still does not show whether the intended outcome occurred. Browser source text also misses responsive layout, rendered controls and problems that appear only after the page has loaded.
How EVO approaches it
Use practical tools for focused tasks
The development tool set includes calculation, selected table inspection and aggregation, text search and comparison, selected document reading, memory search, time conversion and selected web reading. These provide actual results for the assistant to work from. A specialist label changes the perspective on a task; it does not grant a new ability to access your computer.
Work through supported application actions
Built-in apps offer direct user controls and supported EVO proposals. For example, a proposed note or task change can be inspected before application, then checked against the saved result. Available actions differ by app. The important link is from your instruction, through the specific proposed change, to an outcome you can read back.
Inspect the page that actually rendered
Visual Web Inspection opens an isolated browser and preserves screenshots alongside rendered-page information, console errors and failed requests. Desktop and mobile-sized observations help identify layout issues that source text cannot show. The recorded public example contains real page captures and rule findings; it does not claim that an AI visually reviewed those screenshots.
Keep action states meaningful
An inspection can finish partially, a proposal can remain pending, and an external result can be unknown. EVO preserves those distinctions rather than replacing them with a generic success message. Stop controls prevent further supported work; an interrupted operation with an uncertain outcome needs inspection before anyone tries to repeat it.
A concrete example
ILLUSTRATIVE WORKFLOW · NOT A CUSTOMER RESULT
Illustrative workflow: inspect a mobile page
You ask EVO to check a public product page at desktop and mobile sizes before making a decision about its layout.
Capture the rendered page at the selected sizes and keep each observation with its URL and capture time.
Review a concrete issue against the screenshot and relevant page information, separating observed facts from suggested causes.
Choose whether to investigate a safe interaction, discuss a selected website file or leave a change for later review.
What you take away
The useful deliverable is an evidence-backed issue list with inspectable captures and an honest record of what was checked. It is stronger than an unsupported claim that the website looks fine, while leaving the next action in your hands.
Your choices
- Choose permitted tools, files, URLs and supported application scope for the request.
- Review required action approvals; inspection permission does not authorise login, form submission, purchases or deletion.
- Cancel supported runs and inspect their saved results before continuing or retrying.
Current scope
Implemented foundation
- An isolated browser inspection produced a real report with captures in September development testing.
- General computer control is not a public feature. Newer source-capture qualification still has a network boundary blocker; it must not be confused with that historical example.
Next milestones
- Public Alpha access, unrestricted control of arbitrary installed apps and a complete everyday browser replacement are not available.
- Broader interaction coverage and real cloud visual-review quality remain separate validation work. A browser audit is not a complete accessibility certification, and a saved screenshot is not proof that every control works.
These are development capabilities, not a public release. See platform availability before requesting a trial.
Platforms and availabilityRelated questions
What can EVO do on my computer?
The Mac development build can read selected material, use supported tools and prepare changes in built-in apps for you to review.
Available actions have a defined target and scope. Supported browser inspections and application changes follow their own controls.
EVO can turn selected task information into a proposed change; you inspect it and check the saved result after approval.
Choose permissions, review consequential actions and use Stop to prevent further supported work.
This is not unrestricted control of every Mac app or website. This public website does not operate your computer, and public App access is not open.
Can EVO inspect the website people actually see?
The Mac development build can load a rendered page and preserve desktop and mobile-size screenshots alongside page structure and recorded findings.
This captures the result of the page loading, rather than treating its original HTML as proof of its final appearance.
An inspection can show a narrow-screen overflow or a small control with the page, viewport and captured evidence attached.
Choose the page and inspection scope. Cloud review of selected screenshots requires a separate data-sharing choice.
The published example demonstrates browser capture and rule findings. It does not qualify model visual judgment, every interaction, logged-in pages or full accessibility compliance.
What practical tools can EVO use?
Supported tools include calculations, selected table analysis, text search and comparison, selected document reading, time conversion and scoped app proposals.
The tool workflow operates on material authorized for the task and returns recorded results that can support the answer.
EVO can total a selected numeric column or compare two selected text versions, then explain the result using that output.
Choose source material and supported access. Review an app proposal separately before applying a change.
The tool collection has defined limits. Public-page text reading is not visual inspection, and selecting tools does not grant arbitrary file, website or account access.
Which actions require my approval?
Supported changes with meaningful consequences need the applicable action review; reading selected material does not grant permission to modify or send it.
Some low-risk supported actions allow revocable reusable permission. Deletion and other consequential changes require a fresh review of their target and effect.
Preparing a task or message can produce a proposal, while applying the change or sending the message is a separate decision.
Inspect what will change, narrow the scope, approve when ready or revoke existing permissions.
Not every proposed external action is implemented. A clarification answer, saved preference or old approval never creates an unsupported capability.
Can I stop a task and return safely?
Saved results can survive a restart in tested internal flows. This does not mean every interrupted task can finish automatically.
A recorded calculator test kept 6 × 7 = 42 when the final explanation timed out. This is a narrow recovery check, not evidence of general task success.
Unknown external actions must be checked before retrying. Complete App recovery remains under qualification.
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.