Agentforce Vibes

You will notice the difference on org metadata. A general agent guesses at your object model; this one queries it, because Salesforce hosts the servers that answer those questions and wires them in for you. The deciding daily trait is that specificity, since the failures that waste an afternoon in this ecosystem are almost always about metadata the agent could not see.

Pick it if Apex, Lightning Web Components and org configuration are the bulk of your work. Pick Cursor when your Salesforce code is one project among many and you want one editor for all of it.

The failure mode is a setting. Session modes run from asking every time, through a configurable allowlist, to bypass, and the third option exists because someone found the first two tedious. On a tool with terminal execution and multi-file writes, the tedious options are the safety model, and a per-session toggle is the kind of control that gets flipped once and never flipped back.

What it does right: Plan Mode changes no files until the plan is approved, which separates the expensive mistake from the cheap one.

1. Context gathering is unusually well posed: instead of embedding a repository, it calls Salesforce-hosted servers for org metadata and API context, so the retrieval problem becomes an API problem with a correct answer. 2. Edit application goes through inline diff review, so every change is seen before it lands. 3. Repository-level Rules and Skills give instructions a versioned home.

No benchmark is claimed. The observation: naming Mastra as the orchestration engine is more disclosure than most vendors offer, and it is still not enough to reproduce anything.

The renames are the tell, and they are a good tell. Salesforce is folding developer tooling into whichever brand it is currently selling to the board, which means the product keeps its funding as long as that brand does, and Agentforce is the brand. Distribution is the moat and it is enormous: every org is a captive install base, and the extension is bundled rather than sold.

Likely path: another rename, not a sunset. Position: safe to build on, provided you treat the product name as disposable and the platform underneath as the actual commitment.

The demo is competent and beside the point. What matters is that this is listed free and included with a subscription we already hold, so sixty seats adds nothing to the invoice and nothing to the procurement queue. The connectors an administrator must switch on in Setup mean access is centrally governed rather than configured per laptop. Identity and retention inherit from the platform contract, which legal has already reviewed.

Onboarding is half a day for anyone already writing Apex. Approved.

There is almost nothing here to bend. The extension is closed, the inference runs on a platform I do not control, and I cannot point it at my own key or my own hardware. The model picker offers a list, which is a menu rather than a choice. Telemetry, retention and routing are decisions somebody made for me in a different building.

The grudging part: Rules and Skills live in the repository as files, so at least the instructions are version controlled and travel with the project. That is a small piece of ownership in a product that offers no other.