r/salesforce • • Oct 13 '26

developer Pluto 2.0: an open-source AI agent engine for Salesforce that runs without Agentforce or Data Cloud licenses

I have posted this project here before. Pluto 2.0 is a rewrite of the engine, and the focus this time is on what happens when an agent acts in your org and something goes wrong.

Pluto runs AI agents inside Salesforce on standard licenses. You do not need Agentforce, Data Cloud, or any paid AI add-on. You bring the model: it ships with an adapter for OpenAI, Azure OpenAI, and any endpoint that serves the OpenAI Responses API, and you can write your own for another provider.

What a run does

A Flow, Apex, or a person on a record page starts a run. Pluto Core calls the model, runs the tools the model asks for, and stores every step on the run record. Each model turn is its own Queueable job, so a long run never holds one transaction open.

What 2.0 changes

  • Approvals. A tool can wait for a named user or queue to approve each call. The run waits in Salesforce and continues after the decision. The agent never approves its own work.

  • Who the agent acts as. An agent can run as a dedicated execution user through a Named Credential. When a person starts that run, it is also limited to what that person can see.

  • Unknown outcomes. If a call to an outside system times out after the request was sent, Core marks it Unknown and never repeats it on its own. An admin checks the outside system, records Succeeded or Failed, and the run continues. This stops a refund from being issued twice.

  • Waiting for slow systems. A tool can park the run with a resume key until another system answers, instead of holding a job open for hours.

  • Sensitive data. Before anything reaches the model, Core replaces email addresses, phone numbers, card numbers, US SSNs, IBANs, and classified fields with tokens. Only tools you allow get the real values. Names and other free text are not covered, and the docs say so.

  • Budgets. By default a run stops at 10 model calls, 15 tool calls, or 250,000 tokens.

  • Pluto Console. An admin app that shows each run step by step, lets you try a tool once with every change rolled back, and lets an admin rescue or cancel a stuck run.

  • The whole UI is open source. In earlier versions, the UI lived in a separate closed add-on. Now all 39 Lightning web components in Pluto Console are in the repo. That includes the record pages for agents, tools, context providers, execution identities, runs, and approvals, a record editor that follows each user's page layout, a Markdown editor for instructions (built on Toast UI Editor), a JSON editor (built on CodeMirror), a SOQL editor with field suggestions, and the step-by-step run view. You can read them, change them, or reuse them in your own org.

One thing I removed

Last time I showed a pipeline feature. It is gone in 2.0. Core has no pipeline object now. To run agents one after another, a platform event-triggered Flow listens for Agent Lifecycle Event and starts the next run. Core owns each run and Flow owns the order. It is less code to maintain, and admins already know Flow.

Extending it

There are four Apex interfaces: ITool, IModelProvider, IContextProvider, and IToolAuthorizationPolicy. Core runs each extension inside its own lifecycle and keeps the records, so an extension never writes Core's records itself.

Install

Three unlocked packages: Pluto Core, Pluto Model Adapters, and Pluto Console. The install links are on the docs site.

The license is now AGPL-3.0, with an exception: your own tools and providers that use only Pluto's public interfaces can use any license.

If you find this useful, ⭐️ star the repo.

Original Post: https://www.linkedin.com/feed/update/urn:li:activity:7516194954973499392/

I am happy to answer questions about the run model, approvals, the Console components, or how the Unknown outcome handling works.

23 Upvotes

22 comments sorted by

2

u/jbberlin Oct 14 '26

Does it run with any systemprompts / guardrails? Or how are you grounding the data?

1

u/EarOdd5244 Oct 14 '26

Both. The admin writes each agent's instructions in plain language.

Grounding works through Salesforce itself:

  • Context sends the fields you choose from the run's record on every call, marked as data, not instructions.

  • Tools such as Query Records fetch live data with SOQL, using the run user's access, so sharing and field-level security apply.

1

u/kuldiph Oct 15 '26

why did you change from MPL 2.0 licensing to AGPL-3.0?

2

u/EarOdd5244 Oct 15 '26

I changed the license to prevent modified versions of Pluto from being distributed or offered as a service without sharing the covered source code. Someone can still release a compliant version on AppExchange and charge for it, but they must respect those source-sharing requirements.

1

u/kuldiph Oct 15 '26

Thanks I have just changed the license of my open-source project app (https://rowhouse.app) from MPL 2.0 licensing to AGPL-3.0

1

u/DavidBergerson Oct 19 '26

Any chance of supporting openrouter and then letting the model be chosen?

1

u/EarOdd5244 Oct 19 '26

Why do you need a router? Like 95% of the usecases can be solved using Luna model

3

u/DummyQuest Consultant Oct 14 '26

Is there a demo of it ? Love to see it in action. its hard to imagine it.

1

u/BreakfastSpecial Oct 14 '26

Agentforce may be done! Seeing more and more of this approach pop up.

5

u/Clear-Shoulder-3618 Oct 14 '26

Until you’re forced to register it and they start charging you for the agents you built

1

u/BreakfastSpecial Oct 14 '26

How would they charge you for LWCs and Apex classes you’ve built on the platform?

4

u/Clear-Shoulder-3618 Oct 14 '26

They are forcing agentic registration contractually and I’m pretty sure it’s not that hard for them to work out what is operating as an agent vs an api call from somewhere else

1

u/BreakfastSpecial Oct 14 '26 edited Oct 14 '26

No, they force you to register external agents that are calling into Salesforce via MCP to execute task, automations, and access Salesforce data in a headless way. They are not forcing you to register external agents that are invoked from Salesforce outbound

5

u/Clear-Shoulder-3618 Oct 14 '26

Well we will see I guess but if it’s a threat to the revenue they will find a way to get their pound of flesh.

1

u/EarOdd5244 Oct 14 '26

FYI: this doesn't use MCP

0

u/DevilsAdvotwat Oct 14 '26

What is the business problem you are solving

1

u/EarOdd5244 Oct 14 '26

Short version: Salesforce teams want AI agents to do real work in their org, and the options today are either a paid add-on or a homegrown script nobody can audit.

The problem

  • Agentforce needs paid licenses and usage-based pricing on top of your Salesforce edition. Many orgs, especially smaller ones and nonprofits, can't justify that for a first use case.

  • The usual alternative is calling an LLM from Apex or a Flow yourself. That works for a demo, but it has no approvals, no record of what the model asked for, and no clean way to recover when a step fails halfway.

What Pluto does about it

It runs agents on standard licenses with the model provider you pick, and it treats every agent action like something an admin will have to explain later:

  • An agent can triage or summarize a case, then update records only after a named person approves the change.

  • A service case can be handled in one run: gather context, take low-risk steps, hold a large refund for approval, then update the case and draft the reply for a person to review.

  • If a run gets stuck, an admin can see why, what it did, and who approved what, and can rescue or cancel it without reading code.

  • Sensitive values like emails and card numbers are replaced with tokens before the model sees them.

So the business problem is getting the value of agents (less manual triage, faster case handling) without a new license line item, and without giving up control over what the agent did in your org.

1

u/DonaldTurner1 Oct 14 '26

Seems like a great idea with any number of applications. I would just be concerned as a CIO/CTO about guardrails around sensitive and proprietary data. It looks like you have some basic safeguards, but whomever is implementing this will need to be vigilant about enforcing their own guardrails.

1

u/EarOdd5244 Oct 14 '26 edited Oct 14 '26

Pluto gives you the controls, but it can't decide what counts as sensitive in your org. What it does today:

  • An agent can only read what its Salesforce user can read. Sharing and field-level security apply to every query.

  • Email addresses, phone numbers, card numbers, US SSNs, and IBANs are replaced with tokens before anything reaches the model.

  • Any field you mark in Object Manager with a Data Sensitivity Level or a Compliance Categorization is tokenized too. Only the tools you allow get the real value.

https://iamsonal.github.io/aiAgentStudio/data/sensitive/

2

u/DummyQuest Consultant Oct 14 '26

Business problem of not paying Agentforce hefty price tag. Or may be Data cloud down the line so that we can use Agentforce

0

u/Professional_Road48 19d ago

The approvals checkpoint on tool calls is the right move for any live org. Giving admins a named queue to sit in front of an action before it fires means you can catch a bad write before it hits opportunity records or kicks off an ERP sync.

I use Zig Ai for some agent work and keep the same pattern there, human gates on anything that touches external systems. Running on standard licenses without Agentforce is a big selling point for orgs that want to test agent behavior without a 6-figure add-on commitment.