Karthik Kalyanaraman
@karthikkalyan90
Helping companies build highly reliable AI agents | Building @langtrace_ai - open source LLM application observability | DMs open if you need help with AI
All it takes is one tweet. This tweet inspired me to build 👇 x.com/karthikkalyan9…
We're building a @v0 slackbot. It can build any app or give you expert answers on @vercel, @nextjs, etc. In the process we realized Slack is like… the perfect AI agents platform (@benioff is sitting on a goldmine) Here's the open source recipe for how to build AI agents like…
Just shipped fine-grained access controls to our Agent Slack bots. Now if someone tries to add a bot to a channel they shouldn’t, the bot just leaves. And no, the agent doesn’t decide that, it’s deterministic logic, like how we used to build software before.
Claude code writing clean commit messages is so satisfying to see the git log
I think one second order effect of generative coding is, gaming is going to blow up in a big way. Know a lot of gamers who wanted to be game developers but never became one because of how steep the learning curve is to even become a decent game developer. Generative coding…
Bearish on prompt engineering for text/code generation Bullish on prompt engineering for image/video generation
The point of agents that run in the background is not “oh it’d be faster if I did it myself”. It’s to simply offload work that needs to get done but not necessarily immediately. This allows one to scale by offloading tasks to machines that work when you sleep.
The underrated aspect of Claude code that no one talks about is that, when using Claude Code, your PC acts as the storage layer that holds all the context.
Consistently noticing Google search AI overview returning more accurate results vs ChatGPT with web search.
Best thing I did was actively surround myself with builders I used to waste my time with people that talk but don't build Talkers cling on to builders to suck their resources like leeches They will put you in giant email threads, Zoom calls, endless DMs, to talk ideas and…
It's my turn to say now, RIP Frontend engineering
The bitter lesson is widely misapplied IMO. It's essential to realize 3 things: (1) The undeniable lesson is that you learn best by actually solving problems. If you're NOT throwing away prototypes, are you making progress? Generalize gradually. Scale one dimension at a time.…
In the long run, don't even build the agent or ask it anything concrete. Just go touch grass or something. Signed: The bitter lesson.
And what better product surface to build and deploy agents than @SlackHQ . Here's a quick demo of our Slack bot Zest capturing, enriching, writing personalized email and drafting it to my mailbox in our lead funnel. 👇
The best teams building agent typescript sdks are lean. - aisdk is 3 - ax is 1 @dosco
if i told you the ai sdk team only has 3 members would you believe me because i wouldn’t i thought there were at least 50 elves and a wizard
What a crazy 72 hours it has been I was itching to switch over to windsurf after cursors price changes and recent sluggishness of the product experience. I decided to pause after hearing windsurfs leadership left for big tech. Now again I have decided to switch over to…
💯 agree with this take. MCP does not replace tool calling. MCP enables data portability. MCP is what is going to make memory portable and not some general protocol for memory standardization and portability.
I've been seeing a lot of people I respect use, and think about MCP wrong - I don't think you understand. me and @theo were talking about how MCPs have a use-case problem - and that's kinda true, but MCP is _not_ meant to replace tool calling etc. the main unlock of MCP is…