
I ship things people love using • mts @mem0ai - https://xitter.cf/t.co/n9C3OZSXkr (30k+ mau) - https://xitter.cf/t.co/oPkkjxsyZC (20k+ downloads) - https://xitter.cf/t.co/acE2EdY8ZX
Joined March 2023
- Tweets17.8K
- Following979
- Followers10.4K
- Likes118K
Kartik retweeted
your AI agent believes everything it reads and sometimes reads "2" as "20".
now give it your credit card.
here's the system design that makes that safe:
→ the agent never sees the card
→ single-use cards: one shop, one amount, 30 mins
→ 7 guardrail layers, only 1 trusts the model
5 min breakdown 👇
Kartik retweeted
software engineers are going to have to tackle a new set of problems to unlock powerful multiagent systems to solve the world's hardest problems - right now is one of the most interesting moments in history to be an engineer.
Kartik retweeted
Anthropic is now recommending that companies REMOVE unnecessary subagents from their AI systems.
This is a pretty significant shift in agent architecture, with their team finding that a single agent equipped with skills can frequently outperform complex multi-agent systems, and one customer seeing roughly 2x faster execution.
The emerging rules of thumb:
→ Skills: Teach the agent HOW to do something, including procedures, expertise, and instructions.
→ Tools / MCP: Give the agent the ability to DO things through APIs, actions, and live data.
→ Subagents: Use for parallel work, isolated context, or tasks a single agent struggles with.
The interesting part is progressive disclosure. Instead of spawning specialized agents or stuffing everything into a giant prompt, one agent discovers and loads skills and tools as needed.
Their advice is to fold existing subagents into the main loop, turn their instructions into skills, expose their actions as tools, and run evals to see if performance holds up.
As models have gotten smarter, improving agent architecture is becoming less about what you can add and more about what you can delete.
claude.com/resources/article…
Kartik retweeted
I wanted macOS Screen Time on my Ubuntu
everything i tried was heavy or ugly, so i built my own
Daymark: 8.4 MB binary, no electron, no account, no network code, ~0% CPU in the background
Open source 👇
Kartik retweeted
Disagree.
The moat is the data flywheel, proprietary feedback compounding with usage, captured by agent training platforms.
"SLMs make this sharper: when model access is becoming less distinctive, unique data and the learning system around it carry more of the advantage." 👇
Kartik retweeted
Save Mac storage without deleting anything
Introducing TwinFold: Open source Mac app that stores identical files once
Every file stays exactly where it is and keeps working. It just stops taking up space twice.
Free & Open sourced- github.com/Himanshu-Sangshet…
Kartik retweeted
you don't need next.js + vercel + supabase anymore
- next.js → tanstack start or vinext
- vercel → workers
- supabase postgres → d1
- supabase auth → better auth on d1
- supabase storage → r2
- realtime → durable objects
- redis → kv
- background jobs → queues + cron triggers
one worker, one bill, ~$5/mo
Today, I'm launching llmdojo.dev:
- The hands-on way to learn AI engineering: LLMs, RAG, agents, evals and inference.
- 50+ interactive labs. Tweak tokenizers, attention, embeddings and KV caches live.
- Train a neural network in your browser and watch it learn.
- Build agentic workflows with tool calls, memory, guardrails and bounded autonomy.
- Ship RAG that works: chunking, hybrid search, reranking, and LLM-as-a-judge evals.
- Production AI: model routing, fallbacks, quantization, caching and cost per request.
- 490+ interview questions, reported from OpenAI, Anthropic, Google, Meta, Amazon, Microsoft, Mistral and 50+ more.
- Every answer is cited from papers and books, or measured on real models.
Kartik retweeted
System design in 6 lines:
Slow reads → add a cache
Slow writes → add a queue
Too much traffic → load balancer
DB struggling → read replicas
Files → object storage + CDN
Everything breaks → retries, timeouts, logs
Start here. The rest is details.
Speaking of security, we created a registry for building OIDC configuration components.
Pick your providers, form and validation libraries, and token verifier (powered by jose). Then run one command to copy everything into your app.
I've built these a few times before. I know how annoying they can be to get right. Hope this helps.
ui.shadcn.com/oidc
It's time to retire long-lived static credentials.
We surveyed 1,000+ SaaS vendors and found only 8.4% support secure auth. This is our call to action and how we're doing our part.
vercel.com/blog/death-to-lon…
Kartik retweeted
introducing pwn.watch 👀 one place for following all the live security incidents
it serves rss + llms.txt so u can paste to your clankers
tell them to watch it on a schedule and sleep at night 😴
100% free but kitze.io/sponsors will appear on it ❤️
Kartik retweeted
> wake up
> internet on fire
> be on cloudflare
> 98% sleep score
> customers happy
> zero downtime
> keys safe
An urgent notice from the Railway team
blog.railway.com/p/security-…
Kartik retweeted
October has been an absolute nightmare for software
> Railway - customer secrets exposure
> LiteLLM - malicious PyPI + Docker releases
> Zeabur - infrastructure breached
> OpenCode - AI API keys exposed
> OVHcloud CLI - official binaries backdoored
> Rank Math PRO - malware in official plugin
> TeamUpdraft - customer data compromised
> ConnectWise - cloud backup identities compromised
> Tensorlake - npm package infected
> SubQuery - backdoored npm package
> GhostAction - GitHub repos with malicious workflows
> PHP - critical RCE vulnerabilities
> Node.js - security vulnerabilities patched
> eMudhra - certificate authority keys compromised
> Tailscale - eMudhra incident
At this point, the biggest security risk might not be the code we write, but the code we trust...
Kartik retweeted
Today, @agentmail has processed over 1 Billion emails.
A year ago, we processed under 20 million.
So we figured it was time for AgentMail to grow up a little too :)





























