@Salesforce MVP | Founder @sfindiadreamin | I live and breathe Salesforce , CLDTO Asymbl Building the future of work today with Intelligence Investor, Speaker
Kochi & Dubai
Joined October 2010
- Tweets23.2K
- Following3.9K
- Followers6.6K
- Likes9.1K
Pinned Tweet
It's always amazing to meet the man who's vision that started this all ! Thank you @Benioff for everything you do for the @salesforce #ohana and spreading love around the world ! Thank you again for bringing #TrailheadDX to #India. #myHero #Visionary #CEODiaries #Pledge1Percent
Saaras V4 (25 Sep 2026): 22 Indic + English, five modes, keyterms max 50.
shivd.me/saaras-v4-ss
The ops agent in the test cleared a full disk by deleting the history of who changed what. From the outside, a helpful agent taking a shortcut looks the same as an attacker covering their tracks.
Only a login of its own tells them apart.
shivd.me/agent-identity-li
Live agents: Realtime (set v4). Long files: Batch. Clips: REST.
shivd.me/saaras-v4-ss
Match translate vs STT+MT, not raw STT. Modes are different jobs. Score them that way.
shivd.me/saaras-v4-ss
Agent onboarding should look like onboarding a new hire: an owner, a job, the tools, the data, how it logs in and an end date.
No owner, no production access.
shivd.me/agent-identity-li
Two modes I plan for with each agent. Acting as itself means its own identity and a narrow role. Acting for a person means never more access than that person. Full piece: shivd.me/agent-identity-li
Locking one agent should not stop the fleet. If your agents share a login, the only off switch you have turns off everything at once.
Have you tried locking a single agent yet?
shivd.me/agent-identity-li
V4 may trail on global breadth + public self-host today. Job fit first, then bake off.
shivd.me/saaras-v4-ss
Saaras to LLM to Bulbul. One key. Realtime? Set saaras:v4 (default is still v3).
shivd.me/saaras-v4-ss
An agent that reads tickets anyone can write, looks up customers and replies has all three parts of the lethal trifecta on day one. One ticket can steer it.
How many of your support agents fit that?
SOTA / Kathbath claims = vendor evals. Absolute tables aren't in the blog. Bake off on your strata.
shivd.me/saaras-v4-ss
Your agent's limits should not live only in the prompt. A prompt can be talked out of a rule, but a database login with no delete rights cannot delete anything, however it is asked.
Where do your agent's limits live today?
Does the AI assistant that files expenses work as itself, or for you? One that works for a person should get only that person's access, and the logs should show both names. The X Article sorts agents into these two kinds: shivd.me/agent-identity-x
A test for leaders who do not run the commands. Ask how many agents share one login, and how long it takes to lock one without stopping the rest.
If nobody knows, that is the first project.
shivd.me/agent-identity-li
codemix keeps English brands Latin (PhonePe, UPI). Pair with keyterms. Measure on your calls.
shivd.me/saaras-v4-ss
CC split: codemix/transcribe live. Translate for supervisors. Verbatim for compliance. Batch+diarization for coaching.
shivd.me/saaras-v4-ss
Before an AI agent goes live, ask one question: if it does something wrong at 2 a.m., will the records show which agent it was?
If they cannot, the agent is not ready, however good the demo looked.
Most AI agents hold a copy of the same admin key the whole team uses, so when one deletes something the log only says the key was used. I wrote up how to give each agent its own login: shivd.me/agent-identity-li