The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

How an MCP tool cut triage of 600 test failures to about 90 minutes (opens in a new tab)

You will learn how Salesforce engineers split deterministic code from AI reasoning in an MCP workflow that clusters and reassigns test failures, and which guardrails prevented duplicate work items and misrouting.

Why read this

The reasoning is useful even if you never touch the GUS internals.

  1. Retrieve failures
  2. Gather context from stack traces
  3. Detect patterns or apply categories
  4. Reassign individually, in bulk or by team
The workflow runs through four stages, from retrieval to reassignment

Salesforce’s engineering team faced over 600 test failures triggered by the retirement of the SOAP API login mechanism. Expected failures and genuine regressions could produce similar exceptions and span several scrum teams, so a wrong classification could hide a real defect or send engineers chasing the wrong problem for days. The existing process required manual stack trace reading and reassignment through an interface limited to 50 failures at a time, and it could create duplicate work items or misroute failures.

The team built AI-Assisted Test Failure Buddy as a Python and FastMCP process exposing eight tools to Claude Code or Cursor, connected to the APIs behind GUS, Salesforce’s internal work item system. The design separates an interface layer of typed MCP tools, a core logic layer that controls API calls, identifiers, parsing, validation, batching, clustering and reassignment, and a support layer for authentication and tokens. The workflow runs in four stages: retrieve failures, gather context from stack traces, detect patterns or apply categories, and reassign failures individually, in bulk or by team.

Grouping was the hardest part. Stack traces offer no stable key for root cause, and the same exception type could mean an expected SOAP login failure in one context and an unrelated bug in another. The team combined deterministic processing, such as regular-expression matching and a preset recognizing strings like INSUFFICIENT_ACCESS, with AI reasoning reserved for novel traces, unmatched clusters and ambiguous ownership. To avoid duplicates, the tool assigns related failures to one existing work item and uses explicit failure IDs in place of the broader interface action that had caused misrouting.

The estimated two or three days of manual triage for one 600-failure work item fell to roughly one to one and a half hours for a single engineer. The tool has since been used by three or four teams, though it has no adoption telemetry yet. The article also notes that Claude Code helped build the tool, starting from a markdown design document with human review throughout.

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

Worth reading?

Must-read

Building Custom Objects and Permission Sets with the Salesforce Development Plugin for Claude Code (opens in a new tab)

You will learn how to set up the Salesforce Development Plugin in Claude Code, prepare an org with the metadata-experts and salesforce-api-context MCP Servers, and generate a Custom Object, Permission Sets and a Lightning page as metadata.

Why read this

You will also see why the older Salesforce DX MCP Server is being retired and why deployments should stay with humans.

  1. Create the DX project
  2. Build the Custom Object and fields
  3. Build the Permission Sets
  4. Build the Lightning page
  5. Package the metadata for a human to deploy
The main stages of building metadata with the plugin in the worked example

The article explains how the Salesforce Development Plugin for Claude Code differs from other tools with similar names. It groups Skills, the Salesforce CLI and hosted metadata servers into one toolset, while the Salesforce DX MCP Server reaches end-of-life on November 2, 2026, and Salesforce in Claude is aimed at end users rather than builders. The author lists the prerequisites: Node.js, Python, the Salesforce CLI and Claude Code, with a Claude plan that includes Claude Code. The org must have the MCP Servers page under Integrations and API Catalog used to enable the metadata-experts and salesforce-api-context MCP Servers.

The walkthrough then installs the plugin with the claude plugin install command and runs the setup command to check the org connection. The author builds a worked example, The General Store, using prompts that create a DX project, an Equipment Loan Custom Object with picklists, a lookup and a long text field, two Permission Sets, and a Lightning Record Page. He reviews the generated XML to confirm the read, create and edit permissions match the requirements.

The piece closes with advice on safety. It recommends building in a sandbox, Developer Edition org or Scratch Org, keeping deployments in human hands, and giving the agent specific field names and permissions because the model is trained on generic data.

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

Worth reading?

Salesforce unveils AIforce apps linking platform data to Claude and Slack (opens in a new tab)

You will learn what the three AIforce applications are, what each does with Salesforce data, and what the Claude Code plug-in adds for developers.

Why read this

The piece is a brief overview without implementation detail.

AIforce initial release

  • Claudeforce
  • Slackforce
  • Agentforce Coworker
The initial AIforce release is made up of three applications

Salesforce announced AIforce at Dreamforce, a set of applications that connect platform data and workflows to Claude and Slack. The initial release has three parts: Claudeforce, Slackforce and Agentforce Coworker. Claudeforce comes out of an expanded partnership with Anthropic and ships with 37 pre-installed sales capabilities, from prospecting to opportunity management, plus a Claude Code development add-on with more than 40 further tools. Deloitte, GitLab and Legora piloted it, and it is now in beta for all customers.

Slackforce brings Salesforce data into Slack conversations, letting teams combine information from different sources, apply filters and take actions through interactive surfaces. The upgraded Slackbot assistant and Slack CRM feature can update files and create records from simple text commands.

Agentforce Coworker works inside Salesforce’s internal Lightning environment as a digital assistant that uses customer history and activity. According to the company, it needs no data migration or new permission settings, and it recorded 100,000 activations in its first 35 days.

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

Worth reading?

Must-read

Running Apex tests locally so AI coding agents can iterate on them (opens in a new tab)

You will learn why coding agents stall on Apex when every test run needs a Salesforce org, and how a local Apex runtime exposed through an MCP server gives an agent a fast write-run-fix loop.

Why read this

You will also see the boundary the article draws around deployment.

Against an org

  • Deploy class to an org
  • Wait, then start test run
  • Poll until finished
  • Minutes per cycle

Against a local runtime

  • Run tests on the machine
  • Read structured results
  • Fix and rerun
  • Seconds per cycle
Agent loop against a Salesforce org versus against a local Apex runtime

The article argues that AI coding agents stall on Salesforce Apex because Apex only runs inside a Salesforce org, so each test cycle means deploying, waiting, polling and parsing logs, which can take minutes and requires org credentials. Agents then either stop iterating and hand back untested code, or keep going at a high cost in time and tokens. The author’s published benchmark puts four open-source Apex suites, 837 tests in total, at about 1 minute 46 seconds to deploy and run in an org, against 2.4 seconds locally. The piece also notes that Nimbus was renamed renmy runtime in October 2026, with the same binary and the MCP server name nimbus kept.

The proposed fix is renmy runtime, a local Apex runtime that executes classes, triggers, SOQL, DML and Salesforce Flows against an embedded PostgreSQL, with no org, sandbox, Docker or JVM. The author says it enforces governor limits and mirrors platform behaviour such as Test.startTest and Test.stopTest, and that it is not a mock or a transpiler, though it does not achieve perfect parity. Its renmy mcp command runs as a stdio child process of the agent, so no port or credential is needed. The exposed tools include run_apex_tests, explain_failure, get_coverage, get_execution_trace, execute_anonymous and list_test_classes, which return structured results rather than logs to parse. Setup is a one-line install, a test run in the project, and registration with Claude Code, Cursor or GitHub Copilot.

A worked example shows an agent adding a discount rule to an invoice service: it lists existing tests, writes a method and test, runs the suite, uses the failure explanation to find a status filter bug, fixes it, and uses coverage to add a boundary test, all within seconds and without touching an org. The author also connects this to Salesforce Headless 360, where Apex hooks such as InvocableMethod and RestResource become tools for Agentforce or external agents, and says the runtime can test that underlying Apex offline.

The article draws a firm boundary around deployment. A green local run is necessary but not sufficient, because the org holds Permission Sets, managed packages, Validation Rules and other teams’ automation that a repository does not contain. The agent should not deploy on its own. renmy deploy runs local gates, then a real check-only validation in the org before deploying, while renmy release validate and renmy release deploy add a human approval step and an immutable receipt between the two. The Free tier covers unlimited local test runs, and the MCP server is a Pro feature that is free during the public beta.

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

Worth reading?

Build a Claude Code mod to display Salesforce CLI org context (opens in a new tab)

You will learn how to create a Claude Code mod that reads Salesforce CLI configuration files to show your default org, its type, and Scratch Org expiry directly above the command prompt.

Why read this

The guide covers the required plugin structure, event hooks, and testing steps.

The article walks through creating a custom plugin for Claude Code that surfaces Salesforce CLI context directly in the terminal interface. It explains how to set up the plugin manifest, define reactive state types, and structure the directory for hooks and tests.

Instead of running slow CLI commands, the mod reads internal Salesforce authentication and configuration files to determine the target org alias, My Domain, org type, and Scratch Org expiration date. It also tracks which organizations are connected to configured Salesforce MCP servers.

The tutorial details several event hooks that trigger when sessions start, directories change, or tool calls execute. A render hook draws a colored status band above the prompt, using theme-aware colors to distinguish production, sandbox, and Scratch environments. The author includes validation and testing procedures, plus instructions for making the plugin load automatically across sessions.

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

Worth reading?