<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Salesforce on Orlando O'Neill</title><link>https://oneillo.com/tags/salesforce/</link><description>Recent content in Salesforce on Orlando O'Neill</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oneillo.com/tags/salesforce/index.xml" rel="self" type="application/rss+xml"/><item><title>Every Tool, Used by YOUR Agents</title><link>https://oneillo.com/posts/salesforce-headless-360-ai-agents/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://oneillo.com/posts/salesforce-headless-360-ai-agents/</guid><description>Salesforce&amp;#39;s Headless 360 points at where things are headed: every tool in your stack usable by your personal AI agent.</description><content:encoded><![CDATA[<p><a href="https://venturebeat.com/ai/salesforce-launches-headless-360-to-turn-its-entire-platform-into-infrastructure-for-ai-agents" target="_blank" rel="noopener">Salesforce just enabled AI agents to use every single feature in their platform</a>
 via APIs, MCPs, and CLI commands. This is the future.</p>
<p>It isn&rsquo;t that every tool has its own AI agent baked in. It&rsquo;s that every tool can be used by YOUR agents.</p>
<p>I&rsquo;ve been spouting this to everyone at work. In a world where I can have my own personal Jarvis (AI agent), why would I want to use a generic agent that someone else provides.</p>
<p>And the more you use agents, the more you realize that having to touch a GUI becomes the bottleneck in getting work done. This is something developers already know; and I learned it from my experience with scripting languages. Programmatic usage is unparalleled for speed.</p>
<p>I can&rsquo;t wait for the rest of the world to catch up to this new reality.</p>
]]></content:encoded></item></channel></rss>