The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Two VS Code extensions bring visual context back to agent-driven Salesforce work (opens in a new tab)

You will learn what the Metadata Visualizer and Live Preview VS Code extensions show, which metadata types and UI bundles they cover, and how to open them.

Why read this

It helps you judge whether they fit a workflow built on agents and the Headless Toolkit.

Setup and XML route

  • Retrieve long XML file
  • Navigate Setup to change permissions
  • Retrieve updated metadata
  • Commit changes to version control

Headless Toolkit route

  • Query and modify from terminal
  • Edit metadata locally
  • No retrieve after changes
  • Run operations in parallel
Editing a Permission Set with and without the Headless Toolkit

Building with agents lets developers skip many Setup clicks, but it removes the visual context that makes Flows and Permission Sets easy to grasp. The post presents two VS Code extensions, Metadata Visualizer and Live Preview, as a way to restore that context. It frames them as the visual companion to the Headless Toolkit, which combines agent skills, hosted MCP servers and the Headless Experience Layer.

The author describes the Headless Toolkit through a Permission Set example. Working through Setup meant retrieving a long XML file, navigating menus to understand and change permissions, then retrieving and committing the result. Through agents and the toolkit, the same change can be queried and edited from the terminal in seconds, locally and in parallel, without repeated round trips.

Metadata Visualizer renders read-only views of Salesforce metadata and comes with the Salesforce Extension Pack for VS Code. It covers agents, Flows, Lightning pages, objects and Permission Sets as of November 2026, and is opened by clicking Visualize in the editor. Users can analyze in the visualizer and ask an agent to apply changes, and with Agentforce Vibes they can select elements to have the agent edit them. Live Preview covers Lightning Web Components and Multi-Framework UI bundles, using live org data, and HXL widgets, using sample data that can be customized as JSON.

The post closes by suggesting that future interactive widgets could show metadata directly in agent responses, replacing some of these extensions and builders.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

AIforce is a separate Layer from Agentforce, and developers shift to design and review (opens in a new tab)

You will learn how the Headless Toolkit and AIforce differ from Agentforce, and how the developer role is shifting toward guidelines, review and guardrails.

Why read this

The piece is a session recap rather than a technical guide.

Headless Toolkit

  • MCP Servers
  • Headless Experience Layer
  • Multi framework support
The Headless Toolkit has three pieces that together open Salesforce to any agent

The author writes that AIforce does not replace Agentforce. Agentforce remains Salesforce’s own AI, while AIforce is the layer that opens Salesforce to any MCP client or agent, together with partnerships with agent vendors. He lists the Headless Toolkit’s parts: MCP Servers that expose business logic to any agent, a Headless Experience Layer that renders interfaces dynamically inside agents, and support for frameworks such as Angular and React alongside Lightning Web Components.

According to Alba Rivas of Salesforce, as cited in the piece, the classic workflow of creating objects, writing queries, classes, tests and deploying has less time left. The developer’s work moves to design (asking an agent for a solution that follows your guidelines), review (checking that output matches the request), and guardrails (giving the agent knowledge and limits). Building an app that works in a production enterprise environment is the hard part.

The piece also notes that the Claude relationship continues with an existing Salesforce plugin, while OpenAI and NVIDIA also appeared on stage. It describes MCP as becoming a universal protocol used by business users too, and skills as Markdown files that can be shared across a team.

Read the original at dev.to (opens in a new tab)

Worth reading?

Skills admins need to build with AIforce's MCPs, Skills and Plugins (opens in a new tab)

You will learn how MCPs, Skills and Plugins fit together in the AIforce extensibility stack and which new admin skills to pick up first.

Why read this

It gives a roadmap and the training trails to follow.

  1. User triggers a Plugin
  2. Skill fires
  3. MCP executes
  4. Output returns to user
How the AIforce building blocks work together when a user acts

The post introduces AIforce as a new layer of the AI extensibility stack and explains three building blocks. MCP, the Model Context Protocol, is a standard bridge between an AI interface and live systems, data and APIs, so admins can expose flows, APIs and Apex without writing custom code for each system. Skills define the exact steps, rules and formatting an AI needs to complete a task consistently, and Plugins package MCP connectors, Skills and interfaces into a single installable product. It describes a flow in which a user triggers a Plugin, a Skill fires, an MCP executes and the output returns to the user.

The author lists the new admin skills to develop: MCP management, including centralised org-wide connections and Agentic Identity; building deterministic agent logic with Super Agents and Subagents; lifecycle management of Plugins mapped to user roles; and using Agentforce Coworker, Agent Script, Builder Central and Agentforce Vibes for AI-assisted building. The roadmap moves from AI Trust, Security and Governance trails through hands-on work with Agentforce Studio to advanced building and packaging, then ongoing change management.

The article is largely an overview with links to trails, workshops and resources rather than technical implementation detail, so practitioners will get orientation more than hands-on specifics.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?