Everyone is talking
about Agent Force,
but for the developers
in the trenches,
it's all about
Agent Force vibes.
So to keep the good
vibes going, I'm joined
by two developer superstars,
Mohith Srivastava
and Joseph Kuban.
Mohith is the principal
developer advocate
at Salesforce and
Joseph is the global
VP Salesforce platform
architecture at Astound
Digital. Welcome back
to the broadcast, guys.
Thank you so much.
Thank you for being
here. Now, Mo, developers
love their AI tools
like Claude and Codex.
What does Agent Force
vibes bring to the
table? That's an
excellent question, Diana.
And I see a lot of
innovation that our
developer community is
doing with Claude, Code,
Codex, and we all
love that. But here at
Salesforce, we have our
own opinionated way of
doing metadata-based
software development.
And there are skills
that you need. And
what I'm seeing best
developers do is
they are harnessing
their own agents. That
means they're taking
this cloud code,
doing a lot of
work on top of
it so they can
be productive,
like, for example,
writing skill
files, creating
their own MCP tools,
and they're just
harnessing it, right?
We want to make it
very easier for our
entire developer
community, and that's
where I'm excited
about AgentForceWipes 2
.0 that just got
launched, previewed
yesterday at Keynote.
I hope you saw them.
We did. That has one
-click MCP install.
You have different
harness strategies there,
and you can switch
between different models.
You can switch between
different models.
And we're going to
make sure that we give
you a baseline setup
that's very easy to
configure and get
going with all of that
trust and the security
that our enterprises
love Salesforce
for. Awesome. Such
exciting stuff. Now,
Joseph, you're an MVP,
an agent blazer
from your hoodie as
well. And you
implement Salesforce
in your day-to-day.
So you're looking
at ROI, you're
looking at delivery.
How does Agent
Force Vibes actually
change your day-to
-day? Yeah, so we have
incorporated Agent
Force Vibes most
visibly inside of
our innovation lab,
where we work on go
-to-market activities
and showing proof
of concepts to our
customers. If we're
able to spin up
something that
reflects the art of
possible and get
them on board with a
vision, that's where
we're seeing the
biggest bang for Vibes
within the group.
Ultimately, when
you're doing delivery,
you have a little
bit more complexity
with iterations around
testing and ensuring
that you've got
trusted responses and
whatnot. So that,
there's more energy.
But up front, we're
accelerating a lot of
that early work.
Sounds good. All right.
Well, we're hearing
a lot of buzz around
React support within
Agent Force 5's.
Mo, how does this
bridge the gap between
B2C and B2B apps? Yes,
so for traditional
Salesforce developers,
we have always been
using other outside
third party services
to run B2C scale apps.
I'm really excited
about supporting React
now on Salesforce
platform because they
have all the data right
there in Salesforce
platform. And to be able
to just use the React
skills and use Agent
Force vibes to create
these React projects,
they'll be fast
accelerating and connecting
to the data right
away there and
building apps on the
trusted platform,
Salesforce, right?
So it's very trusted
because it's been
running there for like
almost like more than,
you know, 25 years.
So we have been there
in the business.
So our developers
trust this platform.
Only thing is that
they had to do their
own engineering to
be able to like build
these React apps.
Native support, I'm
so excited. And with
Agent Force vibes,
I think it's time
for all of our
developers to just
get out any idea that
they have in their
head and see it
live in their
Salesforce instances.
And being able to
see the clip of that
is so cool. Joseph,
I hear that the
local dev features
are a massive
productivity win, so
there's no more push
and prey to the
server, right? Yeah.
The being able to
control more of your
software development
lifecycle, seeing what
happens when you go
from org to org, right,
and ensure that
you're deploying it,
what it might look
like during deployment.
Developers learn a
lot about what they've
built when they
migrate code. There are
things to be careful
of incorporating for
that accuracy and
reliability. So when they
can see that firsthand
all within one
council and how that's
going, they gain cycles,
you know, and it
builds their confidence
that they're handing
off a good product
to the test team and
to the customer for
a preview. Nice. Now,
Mo, we've heard at
TDX that anything
reusable can become a
skill. How does the
AI remember and how is
it used within the
developer workflow? Yeah,
so, you know, I think
this is something
that all developers
would have faced is,
you know, if you want
to do certain tasks,
and let's say if the
AI sort of not gets it
right at the first
time, and the moment
you start giving more
context and more rules
and more streamlined
instructions, you'll
see that the AI, like,
really behaves well.
So how do you do that
at scale so that you
don't have to repeat
it again? And that is
the concept of skill
files. So with skills,
you are dynamically
loading the context.
And with that,
what I'm seeing is
anything that you
think AI can do
it really well and
follow through,
you'd want to
create a memory
So skills are the
procedural things
that you want AI
to repeatedly do.
Like, for example,
I have a skill to
write good commit
messages and do PRs
when I'm done with
my development. So
I made it a skill.
I now have as a
skill file within my
agent force vibes.
And every time I just
call that skill, it
does the job for
me. So anything you
think is reusable, that
you have worked with
AI, and it's
repeatable now for your
work, you can modularize
it and keep it within
your agent force
vibes or cloud code.
This becomes like a
skill for an agent.
That sounds awesome.
And I heard that
like the number of
lines of code at
Dreamforce was something,
I don't remember
the number, but now
it's up to like 100
million lines of
code. Is that correct?
Yeah, can you
speak to that?
Yeah, so the 100
million lines, I
think it's more
than that by now.
These are the lines
of codes that AI
generated, developers
validated them.
And once they validated,
they vetted them
and they are now part
of the production. It's
not like AI is just
generating slop, but
when you control and put
guardrails and provide
more tools and create
a governance process
on top of it, and
with human judgment in
there, with human in the
loop, you are converting
a lot of these AI
-generated code to
actual production working
code. That's much more
easier on our platform
because we already
have all the metadata
there and our platform
is trusted for so many
years that it just
works, we are seeing
that trend right now,
that it's so easy to get
started on Salesforce
development than ever.
That's awesome. I
mean, it was already
easy, by the way. Yeah.
So this is taking
another step. Yeah.
But again, remember,
production is
unforgiving, right?
So you need that human
judgment in place.
You need developers.
Yep. You need to
vet this code.
You need to establish
this process and
have governance in
place. But once you
have it, you'll see
the magic. Amazing.
Now, Joseph, developers,
I hear they hate
being locked into any
one LLM model. How
are teams bringing
the choices of models
to their workflows?
Yeah, that's actually
very important.
It's very important
from the customer's
perspective as well.
You very well may
likely have a Salesforce
development team
internal or working with
a partner. But a
company may very well
also have its own data
scientist team, its
own data analytics
team. And those groups
may own the LLM. They
may be the ones building
it. We had a recent
customer experience
where we wanted to
build an SDR agent
and get feedback about
how a salesperson is
closing deals. And
the context with the
customized LLM provided
those salespeople
how they were doing
selling relative to that
company's selling
methodology. That
company's process from a
custom LLM built outside
of Salesforce, but
brought into the
agent with vibes and
whatnot. It's so cool.
Important to be
able to have that
personalization. Yeah,
that flexibility. and
flexibility absolutely
okay jinx yeah you owe me
a coat so if you're
a developer watching
right now and you
haven't turned on vibes
yet what's the one
reason they should start
today mo i'll start
with you yes so i think
with the vibes uh i
know we had previous
version of the vibes
but i strongly recommend
that you go try out
vibes uh and just
play with these tools
you know the best part
about these tools is
you play with them
you learn how they sort
of work and see you
You know, how it like
sort of fits into
your developer workflow
and customize them.
So, you know, there's
this QR code that
we'll have on the
screen, scan it, go to
your ARCs, turn them
on, and just play with
it. Yeah, what would
you say, Joseph?
Yes, I think the
expression is, right,
fortune favors the bold.
At this point, it's
not a matter of will
a developer or will
an admin use AI to
configure and code.
It's when you will do
it. You will either
be doing it now or
you will be doing it
in six months or a
year. So you might as
well jump in, embrace
the change, and start
moving in that path.
Fortune favors the
bold. Thank you,
Joseph. Thank you, Mo.
Developers, to learn
more about Agent Force
Vibes, just scan that
QR code on screen
or go to salesforce
.com slash agentforce
slash developers slash
vibe dash coding.