Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

0.22: remove superseded plugin, client and environment APIs

Open
#3,759 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
nodejs, typescript
Domain
api, cli, devtools

Research direction

This is a tracking issue for the 0.22 removals and is blocked by #3748–#3757 and #3311, so wait for those before starting. The scope spans the v1 plugin loader and agentDevicePlugin manifest reading, the @agent-device/testmu entry, createAgentDeviceClient and its managed and daemonLifecycle paths, and the environment and provider wrappers. Done means the removals land, changesets exist for each affected package, and the changelog and docs carry the migration notes.

Written by the indexing model from the issue text.

Description

backlog refactor

Part of #3747. Blocked by #3748–#3757 and #3311.

Removals for 0.22

Plugins

  • Remove the v1 loader adapter and the reading of agentDevicePlugin manifests.
  • Remove the v1 entry and declaration from @agent-device/testmu.

Client

  • The createAgentDeviceClient default becomes daemonLifecycle: 'attach'.
  • Remove managed, along with the client transport's implicit start, replace and timeout-kill paths.

Environment and providers

  • Remove the boundary wrappers that default released public functions to process.env.
  • Remove the remaining hard-coded built-in provider special cases.

Done when

  • The 0.22 changelog and docs carry migration notes for plugin authors (v1 → v2), library clients (ensureDaemon or agent-device/host), and CLI/MCP users.
  • There are changesets for every affected package.
Dominant language
TypeScript
Stars
5k
Forks
334
Avg merge
12h 2m
Merged PRs (30d)
678

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/agent-device

All issues in callstack/agent-device

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.