Skip to content

ComputerPilot MCP v0.7.0 - Cross-Platform Preview

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Oct 16:28
v0.7.0
71514df
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ComputerPilot MCP v0.7.0 - Adaptive Execution Router

ComputerPilot MCP v0.7.0 adds a deterministic, explainable execution-routing layer that helps agents choose the strongest available typed capability before falling back to less structured interaction. The release keeps execution inside the existing typed tools and deliberately does not add a universal arbitrary-action dispatcher.

Highlights

Deterministic execution routing

  • Add a shared execution metadata catalog for filesystem, code/LSP, Git, process, system, Excel, DOCX, PDF, semantic browser, Windows UI Automation, and raw desktop tools.
  • Add structured execution intents and route candidates with explicit determinism, risk, recoverability, capability-confidence, cost, latency, and fallback metadata.
  • Add the versioned deterministic-v1 policy with stable lexicographic ranking and inspectable tie-breakers rather than opaque model scoring.
  • Prefer native structured routes when they are available, such as filesystem operations over editor interaction, LSP rename over typing, native document adapters over GUI automation, and semantic browser actions over raw coordinates.

Read-only routing diagnostics

  • Add execution_candidates for bounded candidate inspection.
  • Add execution_recommend for one deterministic recommendation plus optional bounded explanation data.
  • Enrich recommend_tools with execution metadata from the same shared catalog without changing its existing keyword score/order contract.
  • Keep the live MCP registry authoritative: catalog metadata cannot make an unregistered or profile-excluded tool routable.

There is intentionally no execution_run tool in v0.7.0.

Hard safety constraints

Hard constraints are applied before ranking and cannot be overridden by route scores:

  • raw desktop routes require explicit permission;
  • destructive work cannot automatically fall back to raw desktop input;
  • destructive ambiguous semantic targets fail closed;
  • stale semantic references do not degrade to screen coordinates;
  • unsupported platform/profile capabilities are excluded;
  • macro-preservation requirements eliminate document routes that cannot prove the required fidelity;
  • visual.desktop remains reserved and unavailable in v0.7.0.

Durable workflow integration

  • Upgrade the workflow store to schema v6 with optional structured execution intent metadata.
  • Persist selected route, router policy version, bounded route decision metadata, and bounded fallback history.
  • Persist and validate the selected route before routed workflow side effects begin.
  • Require routed workflow decisions to match the fixed allowlisted action route.
  • Preserve prior behavior for workflows that do not declare an execution intent.
  • Keep uncertain side effects reconciliation-only: the router does not blindly reroute or replay an uncertain operation.

Observability

  • Add bounded in-memory router metrics to server_health, including decision count, no-route count, rejected-candidate count, fallback rate, route distribution, native/semantic/raw usage, latency summary, and bounded recent decisions.
  • Add an English-only Execution Routing section to the loopback Control Panel.
  • Keep routing telemetry metadata-only; it does not retain raw prompts, document bodies, screenshots, credentials, or secrets.

Catalog and compatibility

  • Increase the Windows/full-profile catalog from 148 to 150 tools with the two read-only routing diagnostics.
  • Keep public project/package identity as ComputerPilot MCP / computerpilot-mcp.
  • Keep the protocol-level MCP server identifier ali_windows_agent_mcp for existing clients and tunnel configuration.
  • Keep the v0.6 native document domain, v0.5 semantic browser capabilities, recovery model, durable jobs, and workflow engine intact.

Configuration

New router settings:

MCP_EXECUTION_ROUTER_ENABLED=1
MCP_EXECUTION_ROUTER_POLICY=deterministic-v1
MCP_EXECUTION_ROUTER_EXPLAIN=1

Unsupported policy names fail closed when router APIs or routed workflow steps are invoked; they do not prevent the MCP server from starting.

Packaging contract

v0.7.0 continues deterministic packaging for:

  • computerpilot-mcp-v0.7.0-windows-amd64.zip
  • computerpilot-mcp-v0.7.0-linux-amd64.tar.gz
  • computerpilot-mcp-v0.7.0-linux-arm64.tar.gz
  • computerpilot-mcp-v0.7.0-macos-amd64.tar.gz
  • computerpilot-mcp-v0.7.0-macos-arm64.tar.gz
  • SHA256SUMS.txt

Linux arm64 and macOS amd64 remain deterministic package/updater targets without a dedicated native hosted-runner execution claim. Windows amd64, Linux amd64, and macOS arm64 continue to receive native hosted validation through the repository release gates.

Every release archive contains RELEASE-MANIFEST.json with project computerpilot-mcp, version 0.7.0, the exact source commit, target, file count, and managed-runtime policy.

Known limits

  • v0.7.0 recommends routes but does not introduce a universal execution dispatcher.
  • visual.desktop is reserved for a later visual-grounding phase.
  • Windows UI Automation and raw Windows desktop routes remain capability-gated and are not emulated on Linux/macOS.
  • Browser automation still requires Playwright and installed browser runtimes.
  • Release archives continue not to vendor upstream tunnel-client or Cloudflared executables.

Release evidence

See docs/V0.7.0-VALIDATION.md for local release-preparation validation, cross-platform PR gates, exact-SHA publication gates, and artifact/checksum verification.

Assets 8
Loading