Skip to content

Infrastructure: Add the generalized desktop-mcp management facet #4450

Closed

Description

@JasonVMo

Current status - 2026-11-16

Ready; generic F11 is unblocked by #4491. The first task is the reviewed management transport and scope decision. F8 persisted queries (#4457), F12 attenuated grants (#4456) and the generic attach-only runner handoff (#4491: busy, relinquish, operator preemption, drain-confirmed runner reservation, fresh MCP controller after preemption) are merged; #4448 is closed. None supplies a workload-management transport, so the transport/scope decision (see Scope) comes first and is part of this item, not an external blocker.

The current MCP adapter remains a driver-only verified client: it does not start, stop or recover workloads, build helpers, evaluate config, or run suites. Keep that boundary and the current package name until bounded harness-owned management tools and a compatible migration actually land. Cross-connection session resume and replay remain unsupported (#4491 did not implement them).

Remaining work:

  • A reviewed transport and scope decision
  • A finite declared catalog and opaque run handles
  • Bounded status, results and artifacts
  • Truthful cancel/reconnect semantics
  • A verified transport and scopes
  • A naming/deprecation decision based on publication history
  • Measured discovery cost

Six-tool discovery was measured at 4,691 tokens and 20,277 bytes, well above the earlier proposed 8 KiB target; the per-endpoint values are in the Measurements section of packages/agentic/desktop-driver-mcp/references/current-status.md.

F4 #4437 and F5 #4443 (both closed via #4463) and F9 #4449 (open, ready) gate only the later Storybook facet, not the generic management implementation.

Goal

Let agents check workload status, run approved suites, cancel their runs, and read bounded results through MCP, not only drive UI. When these management tools land, rename the adapter to @fluentui-react-native/desktop-mcp, keeping a driver-only mode and compatibility for existing users. The adapter stays a client: it never becomes the resource owner.

Part of #4435 (plan item F13).

Scope

  • Owner: harness control client and MCP mapping.
  • Paths (under packages/agentic/): a real desktop-test/control implementation and subpath; desktop-driver-mcp server, controller, and package migration; transport extension or descriptor changes only as the chosen design requires.
  • First task: the reviewed management transport and scope decision (below), before implementation.
  • Expose a finite, supervisor-declared catalog: workload status, run an approved suite, cancel an owned run, and bounded result and artifact queries. Review start, stop, and recover permissions separately; operator recovery is not an ordinary agent tool.
  • Return an opaque run handle rather than keeping a model call open for the whole suite.
  • Decide the management transport: a startup-registered authenticated extension on the driver listener, or a separate verified supervisor endpoint in a versioned descriptor. Sharing a socket must not move lifecycle semantics into the driver. Build on the busy/relinquish/preempt and drain semantics already delivered in Add scoped attach-only runner grants and drain-confirmed desktop handoff #4491 rather than introducing parallel ones.
  • Check the npm publication history of desktop-driver-mcp before choosing a deprecation period, and migrate the package and binary names compatibly.

Dependencies

Acceptance

  • The model cannot select config, modules, commands, paths, environment values, or URLs.
  • Each management schema has one source, owned by the harness.
  • Discovery and results are bounded, and measured discovery cost is recorded in the MCP status overview.
  • Reconnecting does not replay a run, and cancellation produces truthful incomplete or settled status.
  • Existing driver-only descriptors still work.

Validation

  • Iterate with focused yarn test <name> in each changed package, then run its yarn format, yarn lint, yarn build, and yarn test. Finish with yarn clean-lage-cache then yarn lage buildci; run yarn lage test-links --verbose --grouped after markdown changes.
  • Add a patch changeset for each changed published package. Update the affected topic section and its status-overview line in the owning references/current-status.md, and affected README/AGENTS guidance, in the same change.
  • Native, provider, or process-topology changes need matching-OS native contracts and the affected consumer lane. JavaScript tests and bundles do not qualify native behavior; hosted capability skips are not passes. Report each check as passed, failed, skipped, not run, or unsupported.

Evidence

  • Current state: "Workload and test orchestration tools" in packages/agentic/desktop-driver-mcp/references/current-status.md, and "Run queries and management" in packages/agentic/desktop-test/references/current-status.md. Per-run evidence lives in pull request descriptions and issues; each package's references/current-status.md keeps a status overview, stable topic sections, and only the latest result per native endpoint with a link.
  • Retired plan: driver-next.md at 0569e1b86, sections 5 (generalized MCP) and 8 (F13).

Activity

  1. JasonVMo commented on Nov 16, 2026

    @JasonVMo
    ContributorAuthor

    Status update: Status: Blocked removed. Generic F11 (#4448) landed in #4491, so it no longer blocks the generic management path. The reviewed management transport and scope decision is still unmade, but it is this issue's own first deliverable, so the body now states it as the first task rather than an outside blocker. The Storybook facet still follows #4449. No acceptance item is ticked.

  2. JasonVMo commented on Nov 17, 2026

    @JasonVMo
    ContributorAuthor

    Fixed by #4510

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions