Intent
Define the goal, boundaries, and expected artifact.
VMLogic Harness / macOS
In development · No public release dateVMLogic Harness is the planned macOS product surface for persistent agent work. It is designed to connect durable project state with apps, browser sessions, files, and tools—then make the resulting actions and updates inspectable.
Relevant project state recovered
02Claims mapped to sources and constraints
03Browser · Files · Analysis · Document
Verified artifact · trace retained
System loop / 01
A harness coordinates the surrounding system: what should be remembered, which tools may act, how progress survives, and what evidence supports the final result.
Define the goal, boundaries, and expected artifact.
Recover only the project state relevant to this decision.
Turn relations and constraints into inspectable work.
Work through authorized apps, browser sessions, files, and tools.
Check the artifact, sources, actions, and unresolved questions.
Store evidence-backed state so the work can continue later.
One workflow / Research brief
The example below is a product-direction scenario, not a claim of current public availability.
“Compare three approaches to persistent agent memory. Produce a concise brief, preserve the evidence, and leave open questions for the next session.”
Load the relevant project, prior decisions, source register, and outstanding questions.
Project stateUse the browser and local files, mapping each claim to its source and timestamp.
Evidence graphDraft the comparison, test constraints, and surface conflicts rather than smoothing them away.
Reviewable draftWrite the artifact, retain the execution trace, and carry forward only supported updates.
Brief + next stateProduct architecture / Design targets
Projects, people, decisions, evidence, and open questions can remain available across sessions without replaying an entire transcript.
The harness is intended to coordinate authorized work across local files, apps, browser sessions, and external tools.
Checkpoints, resumable progress, and scheduled routines are treated as system concerns rather than prompt conventions.
Repeatable methods can be packaged as skills, while results are delivered as real documents, data, code, and other artifacts.
Inspectable by design / 04
The product direction is to keep cognitive state and execution reviewable: where context came from, what acted, what changed, and what remains uncertain.
Recovered state should retain its source and scope.
Tool actions and produced artifacts should remain inspectable.
Consequential actions should expose clear review and control points.
Durable state should remain separable from the selected foundation model.
Supported models, exact permissions, data handling, availability, and pricing will be published in formal product documentation before release.
VMLogic Harness / Product direction
In development for macOS. No public release date has been announced.