Skip to content

0.22: remove superseded plugin, client and environment APIs #3759

Open

Description

@thymikee

Part of #3747. The breaking removals for 0.22. The non-breaking preparation landed in 0.21.x (see "Done in 0.21.x" below).

Each section below is one PR, and each stays under 2,500 changed lines.

Final 0.22 delivery contract

For the extracted first-party plugins, follow the maintainer decision and shared acceptance in #4591. Core may retain only declarative help/docs/schema/catalog and installation-guidance metadata. Do not ship the plugin factory, executable implementation, plugin-only workers or dedicated runtime dependencies in the core npm package. Lazy-loading code that remains in the tarball is not extraction.

Plugin code is installed separately, on demand, by the existing agent-device plugin manager. T3 Code and e2e must use that shared installation/selection lifecycle and machine-readable inventory/recovery, rather than bespoke npm commands or private-store manipulation. Keep current v2 factories and ./agent-device; older manifest/static-registration examples below describe historical preparation and do not override this final distribution contract. Preserve independently required core contracts and local-device code.

1. Plugin v1 (est. 900–1,500 lines)

  • Remove the v1 loader adapter (packages/plugins/src/legacy.ts), the v1 discovery and store branches, the manifest credential and capability fallbacks, and the install-time v1 collision checks.
  • Keep package-export resolution, entry containment checks and registry validation.
  • @agent-device/testmu: remove the v1 entry (src/plugin.ts), its build entry and the agentDevicePlugin manifest declaration.
  • Migration note for plugin authors: v1 manifest → v2 AgentDevicePluginFactory.

2. Managed clients (est. 1,500–2,300 lines)

  • createAgentDeviceClient defaults to daemonLifecycle: 'attach'.
  • Remove managed and the client transport's implicit start, replace and timeout-kill paths.
  • Keep explicit ensureDaemon(), quiesce, CLI/MCP ensuring, remote attachment, and the shared startup helpers they still use.
  • Migration note for library clients: call ensureDaemon() for a detached daemon, or startAgentDevice (imported from agent-device) to own one in-process.

3. Ambient SDK defaults (est. 900–1,600 lines)

  • Remove the process captures in src/sdk/host.ts. Released SDK functions then need an explicit host: Android adb, artifacts, Metro, remote-config and the public Limrun construction.
  • resolveRemoteConfigProfile requires env, and createLocalArtifactAdapter requires cwd.
  • Review refactor: read host settings from HostEnvironment in root src and remaining packages #3751's waived factory boundaries one by one.
  • Remove the SDK entries from R86 PROCESS_ENTRIES (scripts/layering/process-globals-policy.ts).
  • Keep the executable captures and startAgentDevice's documented optional-host capture.

4. Built-in provider special cases

Done in 0.21.x (non-breaking)

Done when

  • The 0.22 docs and release notes carry migration notes for plugin authors (v1 → v2), library clients (ensureDaemon() or startAgentDevice from agent-device), and CLI/MCP users.
  • There are changesets for every affected package.

Activity

  1. added this to the 0.22 milestone on Oct 20, 2026
  2. thymikee commented on Nov 14, 2026

    @thymikee
    MemberAuthor

    Current state: sections 1 and 3 are integrated into 0.22.

    This umbrella remains open. Managed-client removal, Limrun's built-in special-case removal, and the complete migration/release-note rollup are still required.

  3. thymikee commented on Nov 16, 2026

    @thymikee
    MemberAuthor

    Decision: plugin distribution: final 0.22 extraction means separate agent-device-managed installation, not merely lazy loading. Core retains declarative help/docs/catalog metadata, with no shipped plugin implementation or dedicated dependency closure. T3 Code and e2e use the same management owner and observable install/selection/recovery contract. The issue body now states this explicitly; #4591 owns shared consumer acceptance and the approximately 3 MB unpacked-core target. Earlier seam-only/static-registration or v1 manifest wording is historical preparation, not the final requirement. Existing extraction owners, sequencing, host/session ownership and publication prerequisites remain in force.

  4. apex-sentinel-staging commented on Nov 16, 2026

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    The issue describes a planned set of breaking API removals and migration/documentation deliverables for a 0.22 release, with concrete tasks and acceptance criteria, rather than reporting broken behavior or asking for help.

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

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions