[object Object]

The Coming Feature

AgentExchange roadmap: streamlined Agentforce Builder Installer in fall 2026. Partner agents install and appear ready-to-customize in your Agentforce Builder rather than as opaque managed packages. The installer ships partner Topics, Actions, Instructions, and starter eval set as editable artefacts in your org’s namespace, while preserving an upgrade path back to the partner’s canonical version.

Why It Matters

Today’s installation often leaves you with an agent you can’t easily modify — managed-package locks, hidden Apex, and opaque prompt templates. The new installer places partner agents in Builder as starting templates: you can customize Topics, Actions, Trust Layer config, and even the system prompt while keeping the partner’s expertise as the baseline. Diff against the partner version any time to see what you changed and what they updated.

Install flow (Fall 2026):
  1. Click Install on AgentExchange listing
  2. Review declared scopes + cost projection
  3. Choose namespace: customer-owned (editable) or partner-managed (locked)
  4. Pick Permission Set assignment
  5. Builder opens with partner agent loaded as a base layer
  6. Customer overlays go on top; partner updates merge with conflict UI

ISV Implications

Partners can ship agents designed to be customized. The “black-box agent” pattern weakens; the “configurable scaffold” pattern strengthens. ISVs differentiate on the quality of their starting template, the depth of their eval coverage, and the cadence of their updates rather than on opacity. Two new responsibilities for ISVs: publish a clear customization surface (which Topics are safe to override, which Actions must remain canonical) and ship semantic-versioned updates with migration notes.

Customer Benefits

No more “this agent almost works but I can’t modify it.” Configure to your context — change the tone, swap out a default knowledge source, replace a generic Apex Action with your own. Partner updates flow in via a familiar three-way merge UI: partner base, your overlay, partner update. Conflicts surface explicitly rather than silently overwriting your work. Best of both worlds: vendor expertise plus customer-specific tuning.

Operational Considerations

Treat the installed agent like any other production change. Run the partner-supplied eval set in a sandbox first; add your own org-specific cases; gate promotion through your normal change-management process. Subscribe to the partner’s release feed so you know when an update is coming and can schedule the merge.

Common Failure Modes

  • Customizing the partner agent in production without a sandbox copy — partner updates then overwrite your work or fail the merge mid-deploy.
  • Forking too aggressively, then losing the upgrade path entirely. If you change >50% of Topics, you’ve effectively built your own agent and should detach.
  • Ignoring the partner’s eval set and adding only your own — regressions slip through that the partner already caught.

What Changed in 2026

The fall 2026 installer is the third generation. The prior two were managed-package-based and barely customizable. The new model is closer to npm-style dependency management with conflict resolution baked in — a significant architectural shift for the AppExchange ecosystem.

What to Do This Week

Identify one AgentExchange listing you’d evaluate today and ask the partner whether they’re shipping a Builder-Installer-compatible package this fall. Listings that aren’t ready will lag in adoption.

[object Object]
Share