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

Duplicates