[sidharth0612]

Summary

Phase 2 of the provider → app rename renames the API-key permission provider_connect to app_connect. connect_app's description now ends "Requires the app_connect permission." That is the toolkit's only mention of a permission name.

• node/src/tools.ts: connect_app's description names app_connect. No other wording changes.
• node/package.json: 0.10.0 → 0.10.1, so agentmail-mcp can pin a release that carries the new description. See the version note under Release order.
• No permission reads. Nothing in node/ or python/ reads permissions from SDK responses, and nothing names providerConnect, providerShareOwner or provider_share_owner. So the new SDK dropping providerConnect / providerShareOwner from ApiKeyPermissions needs no code change here.
• The Python toolkit has no AgentID tools, so nothing changes there.

Dependencies (why this is a draft)

• Stacked on Rename the provider tools to list_apps, search_apps, get_app, connect_app #67 (phase 1). The base is claude/app-rename-toolkit, and GitHub retargets this PR to main when Rename the provider tools to list_apps, search_apps, get_app, connect_app #67 merges.
• Merge only after agentmail-api phase 2 PR 2a is live in prod (plans/specs/provider-to-app-rename-phase-2-permissions.md). Until then, the API's 403 fix text and the console still call the permission provider_connect / "Provider: Connect". This description would name a permission the user can't find.
• Typecheck-blocked like Rename the provider tools to list_apps, search_apps, get_app, connect_app #67, for the same reason only. npx tsc --noEmit shows the same 9 errors as Rename the provider tools to list_apps, search_apps, get_app, connect_app #67: the five client.apps accesses and the 4 that are already on main. This PR adds none, and it needs no new SDK field because it reads no permissions.
• Releases together with the other phase 2 tooling PRs: Serve connect_app naming app_connect from agentmail-toolkit 0.10.1 agentmail-mcp#64, Name app_connect in the AgentID skill's 403 guidance agentmail-skills#19 and Re-export the skills with app_connect and release 0.5.1 agentmail-plugins#17.

Before marking ready

• Rename the provider tools to list_apps, search_apps, get_app, connect_app #67 is merged, or this PR is folded into it.
• agentmail-api PR 2a is live in prod.

Checks run (node/)

• pnpm lint: clean.
• pnpm build (tsup, with dts): passes.
• pnpm test: 465/465.
• npx tsc --noEmit: 9 errors, the same as on Rename the provider tools to list_apps, search_apps, get_app, connect_app #67 (above).

Release order

Phase 2 of the provider → app rename: the API-key permissions. The spec is plans/specs/provider-to-app-rename-phase-2-permissions.md in agentmail-api. Phase 1 is plans/specs/provider-to-app-rename-phase-1.md.

0. agentmail-api phase 2 PR 2a (not open yet, stacked on agentmail-to/agentmail-api#1512) is live in prod. It accepts app_connect / app_share_owner beside the old names, returns both names, and its error fix text names only app_connect.
1. Phase 1 tooling releases first, or together with this set: Rename the provider tools to list_apps, search_apps, get_app, connect_app #67, Serve the app tools from agentmail-toolkit 0.10.0 agentmail-mcp#63, Rename AgentID providers to apps in the skills agentmail-skills#18 and Re-export the skills with AgentID apps and release 0.5.0 agentmail-plugins#16. Each phase 2 PR is stacked on its phase 1 PR.
2. Toolkit: Name app_connect as the permission connect_app requires #68. Publish agentmail-toolkit 0.10.1.
3. MCP: Serve connect_app naming app_connect from agentmail-toolkit 0.10.1 agentmail-mcp#64. Pin the published 0.10.1, regenerate the lockfile and mcp-manifest.json, then deploy the connector.
4. Skills and plugins, together: Name app_connect in the AgentID skill's 403 guidance agentmail-skills#19 (re-sync backend-contract.json against agentmail-mcp main) and Re-export the skills with app_connect and release 0.5.1 agentmail-plugins#17 (re-export from AddDraftTools #19, release 0.5.1).

The console relabel to "App: Connect" (agentmail-web apps/console/app/lib/permissions-config.ts, a separate phase 2 follow-up) should be live by step 4. The skill tells the user to enable app_connect on the key in the console.

Versions: 0.10.1 and 0.5.1 assume phase 1 publishes 0.10.0 and 0.5.0 on its own first. If both phases release together, publish the toolkit as 0.10.1 (skipping 0.10.0). For plugins, fold the 0.5.1 entry into 0.5.0, drop its "keeps its name" line, and stay on 0.5.0.

🤖 Generated with Claude Code

[sidharth0612]

Dependency links (opened after this PR): agentmail-api phase 2 PR 2a is agentmail-to/agentmail-api#1515 (stacked on #1512), writer flip 2b is #1516. This merges only after #1515 is live in prod.

[sidharth0612]

Gate met: agentmail-api #1515 is in prod everywhere, and SDK 0.5.34 (appConnect/appShareOwner) is published; the toolkit reads no permission fields, so only the description text changes here. Merge after #67 and publish them together as 0.10.1 (or fold into 0.10.0 if #67 hasn't been published yet).

[sidharth0612]

Folded into #67 (commit b98435a) so the rename ships as one release, 0.10.0.