A Salesforce Release Notes Summary, Rethought and Adapted for Agents

A new Salesforce release ships every four months, and Salesforce publishes the full release notes the same day. Reading that page start to finish isn't how most admins actually catch up on a release, though. More often, the wait is for a subreddit thread to fill in with what people are actually running into, or for a roundup blog like SalesforceBen to publish whichever items round out that release's post. Both are habits that fill a gap, and neither is written by Salesforce or sorted by what your specific role needs to act on before the next release lands.

Neither one was built for a second reader either: an AI coding agent that needs to know what changed in the current release before it writes code or config against it, not a person skimming a summary at their desk. A release note is plain text and a forum thread is a wall of comments; neither is something an agent can query as structured data and trust to be current. That's the specific gap the rest of this closes, for both readers.

Disclosure: DenebForce is a ForceNotes.app partner.

ForceNotes rebuilds the release summary around both of those readers: a role- and action-sorted summary a person can read directly from Salesforce's own text; the same data queryable by an AI coding agent through MCP, machine-readable instead of scraped; and a tracker that watches specific Salesforce Help articles for changes after the release ships, the way the MFA enforcement article below keeps getting revised since ForceNotes started watching it.

Reading a release directly, sorted by role and by what needs action

ForceNotes pulls Salesforce's release notes directly rather than starting from someone else's curation of them, then sorts every item two ways: by which roles it's actually relevant to (admin, developer, architect, consultant, analyst, business user), and by whether it's new, worth knowing, or something that needs action before enforcement. That second axis is the piece a subreddit thread or a roundup blog doesn't really give you. A generic "what's new in this release" list doesn't tell you which of those items carry a deadline for an admin specifically, as opposed to a developer or an architect.

ForceNotes' Winter '27 summary is the concrete version of that: every item grouped under 13 topic sections (Automation, Platform, Security, Data 360, Agentforce & Generative AI, and so on), each one tagged by role and by new, worth knowing, or needs action. ForceNotes' stat bar separately reports 18 core topics, the fuller underlying category list; five of those (Customization, Deployment, Development, Experience Cloud, and Mobile & Salesforce CMS) got folded into "Platform" for Winter '27 by Salesforce itself, so they show up inside that one section rather than getting their own. As of this writing (September 1, 2026), the 13 sections add up to 391 individual items, with 58 flagged as needing action, and those numbers will already have moved by the time you read this: Salesforce keeps revising the underlying release notes, and ForceNotes keeps re-checking them. ForceNotes covers the current release and the next one, not a historical archive; we'll come back to what that scope catches and what it doesn't.

A few of the items in that summary stand out enough to name directly, since they're independently confirmed against Salesforce's own documentation. Agentforce moves from something an admin turns on to something that's on by default: Salesforce is auto-enabling the Agentforce platform on a rolling basis for every org with Agentforce access, starting September 2026, for both new and existing orgs. And a new API Catalog, per Salesforce's own developer documentation, is "a curated registry of REST API endpoints that admins can map to custom MCP tools through the Setup UI," bringing APIs from sources like MuleSoft, Heroku, and Apex into one place an admin can publish as a named tool. If you want the Flow and Agentforce changes that don't show up on the mandatory Release Updates checklist explained in more depth, we already covered those separately in The Salesforce Winter '27 New Features That Aren't on Your Release Updates Checklist, and the full Release Update list, item by item, is in Salesforce Winter '27 Release Notes: What Admins and Developers Need to Know. ForceNotes' summary is meant to sit upstream of both: scan the role tag for what's flagged, then click through to whichever piece covers the item in depth.

The same summary, adapted for an agent to query, through MCP

Reading the summary above is still built for a human: open the site, find your role's section, read it. The same underlying data is also built for the second reader from the opening: ForceNotes runs an MCP server so an AI coding agent can pull the release data directly, in place of an agent's training data (which has a cutoff behind the current release by definition) or a half-remembered detail from a thread or a roundup you read weeks ago.

We've written before about what Salesforce's own Hosted MCP Servers are for: letting an AI client reach into a system's data and tools through one standard connection instead of a custom integration per pairing. ForceNotes runs its own MCP server on the same idea, scoped to release tracking specifically.

The endpoint is https://forcenotes.app/mcp, plain HTTP POST using JSON-RPC 2.0, no signup and no API key. Client setup is a few lines of config:

{

  "mcpServers": {

    "forcenotes": {

      "type": "http",

      "url": "https://forcenotes.app/mcp"

    }

  }

}

Point Claude, Cursor, ChatGPT, or Codex at that endpoint and you can ask it directly: "summarize Winter '27," or "what needs action before the next release." It exposes exactly one tool, get_release_summary, capped so a query can't flood an agent's context window with the entire release. Called with no arguments it returns the catalog of releases ForceNotes has summarized; called with a release name (or next / current / preview) it returns that release's overview, its items grouped by topic, and the deadline-sorted list of what needs action, each item carrying a source URL and a freshness flag so the agent (and you) can tell a same-day item from a stale one. ForceNotes also publishes a downloadable Claude Skill file at forcenotes.app/skill.md, meant to be dropped into a Claude Code project so the assistant knows to reach for the tool without being told each time.

The MCP server is labeled beta: the response shape can still change, and coverage is limited to whichever releases ForceNotes has already summarized, so it's not a fit for wiring an agent to a release ForceNotes hasn't covered yet. Calls are also rate limited, 20 a minute and 500 a day, tracked per caller even though there's no signup step (presumably by caller IP, since ForceNotes' developer docs don't spell out the mechanism), so it's built for targeted queries, not for scraping the whole release into a local copy. On the privacy side, ForceNotes states it uses one strictly necessary cookie for bot protection and that analytics is off by default, only loading if a visitor opts in, which matters if your organization's security review cares about that kind of thing before anyone points a client at an external MCP endpoint.

Tracking what changes in Salesforce Help after the release ships, starting with MFA enforcement

There's a third layer on top of reading the release and querying it: watching what happens to the underlying Salesforce Help documentation after the release ships. Salesforce keeps editing those pages long after launch, and there's no changelog and no notification when a deadline moves, a section gets rewritten, or guidance gets pulled entirely. The only way to catch it is to go back and read the same page again, and nobody's job is to do that on a recurring basis.

The clearest example live on ForceNotes' own site right now is the Help article on mandatory MFA enforcement for employee users: ForceNotes has logged 28 revisions to that single article as of this writing, and counting. That's not a policy announcement sitting still. It's a page Salesforce keeps rewriting, and an admin who read it once, when MFA enforcement was first announced, and never went back, is working from a stale version of guidance that's core to their org's login security.

That's what the tracker is built to catch: ForceNotes' Knowledge article tracker lets you add any Salesforce Knowledge article URL, and it's re-checked on a schedule, with an AI-written summary of what was added, removed, or reworded on each pass. Coverage is opt-in, though: the tracker only watches articles you've actually added to it, so it's only as good as what you remember to point it at. The straightforward way to build that list is to work backward from the release summary above: add the source article behind any item your Winter '27 summary flags as needing action, so the two halves of ForceNotes stay pointed at the same things you're on the hook for, instead of asking you to guess in advance which article matters.

The MFA article isn't the only one making this case. Another tracked article, on Salesforce's Connected App usage restrictions, had its entire body removed at one point and replaced with placeholder text, "Modal Body...", wiping out the migration timeline, FAQ, and technical guidance that had been there before. Neither of those is the kind of change a one-time read catches, and neither would show up in a tracker if nobody had thought to add it first.

What this doesn't replace

That's one limit you control by what you add. Here's one you don't: the release window itself. The current-and-next-release scope is a boundary, not just a convenience. Take the retirement of the OAuth 2.0 Username-Password Flow: it was first announced in Spring '26, circulated for months as a Winter '27 enforcement deadline, and then Salesforce moved the actual enforcement date to February 20, 2027, well into a later cycle. Salesforce's own release note text now reads: "Salesforce enforces this update on February 20, 2027. This update was first announced in Spring '26. It was originally scheduled to be enforced with the Winter '27 major release, but we changed the enforcement date." A tracker that only carries the current and next release forward would already have dropped that item from its window by the time the date moved. ForceNotes is built to catch what's coming in the two releases ahead of you, not to stand watch over everything that shipped three or four cycles back.

Even inside that window, a summary layer is still a second-hand read. For anything with a deadline attached to it, the source URL ForceNotes attaches to each item exists for a reason: click through and read Salesforce's own current text before you act on it. ForceNotes' value here is catching the change and pointing you at it, not standing in for the original.

ForceNotes only covers the release-notes and documentation side of a release. Who has access to what afterward is a separate problem; Power User Toolkit's audit tools cover that side, if that's a gap you're also closing.

Reading Salesforce's own release text sorted by role, querying it from an agent instead of stale training data, and knowing when the underlying Help article changes are three different jobs, covered here by one tool instead of a wait for someone else's roundup. Try ForceNotes directly or go straight to the MCP setup covered above.