
cto @steadwing • ex @mem0ai • love open source
Bengaluru, India
Joined April 2020
- Tweets1.4K
- Following843
- Followers2.3K
- Likes28.7K
We are giving Fo emotions, robot action tools, and an MCP so you all can experience this!
AI can think. AI can talk. AI can get things done.
Today, we're giving Fo a way to feel and control the physical world.
- a head shake and a reminder in a lamp to get you going
- nudge your vacuum cleaner for a deep clean
- make your cli call you for updates
Introducing Fo MCP.
AI has escaped the screen.
Dev Khant retweeted
Production incidents expose what a coding agent cannot learn from the repository alone.
Today we're bringing Steadwing into the agent workflow and closer to the evidence from production with our new Agent Skill and Python + Node SDKs.
Dev Khant retweeted
Most production incidents trace back to something that changed recently. A deploy. A config update. A merged PR.
Steadwing connects to your GitHub or GitLab repos and automatically correlates incidents with recent commits, deployments and releases. When something breaks, the RCA shows you which specific change caused it down to the exact commit and code diff.
No more asking "did anyone deploy something?" in Slack. No more manually scanning CI/CD pipelines. The correlation happens automatically as part of the investigation.
Dev Khant retweeted
The AI for incident response space went through two very different eras.
AIOps was about anomaly detection. Structured metrics. The output was a correlation score and an alert. No diagnosis. No code understanding. Remediation was mostly "roll back".
LLM-powered RCA is a completely different approach. It reads logs, metrics, traces, code diffs, configs, and deploy history. It generates a natural language root cause analysis with an evidence chain you can actually verify. It references past incidents. It suggests fixes on code level, infra and CI/CD.
The shift isn't just better models. It's a fundamentally different architecture from pattern-matching on metrics to actually understanding what your system is doing and why it broke.
That's the approach we took with Steadwing to show evidence-based RCA with fixes you can verify and immediately ship.
All set for the big day at @join_ef.
Come say hi if you drop by Demo Day today!
@khant_dev @steadwing
Dev Khant retweeted
“On-call engineers shouldn’t exist.”
@Abejith (ex-Freshworks) said it. @khant_dev (ex-Mem0) had lived it.
Weeks later: live with real teams.
Demo: a bug a team couldn’t triangulate for years → root cause in seconds.
Most RCA tools fail.
Watch out for @steadwing at @join_ef Demo Day 👀
Dev Khant retweeted
30 alerts in 2 minutes. Your on-call engineer opens Slack and gets overwhelmed.
It's rarely 30 problems, usually one issue causing a chain reaction.
They end up triaging each alert & 20 minutes are gone.
We group alerts into 1 incident & give root cause for it.
We’re excited to share @steadwing at Entrepreneurs First @join_ef Demo Day on April 29, 2026.
It’s a special milestone for the team, and another step toward the future we believe in.
Let’s make production software self-healing! – at San Francisco, CA
Dev Khant retweeted
we rewrote our entire memory system 3 times before it stopped embarrassing us in benchmarks
92.4% on LongMemEval. #1 across every LoCoMo category.
here's the mass deletion of working code arc nobody asked for 🧵
Dev Khant retweeted
Gearing up for the @Aiplus__ Renaissance 2026 🚀
Drop by if you are around!
Dev Khant retweeted
The AI SRE Watchlist grew to 50+ followers on LinkedIn! I updated the website with multi select filter, CTA, 6 new tools @stackgenai , DagKnows, ProdRescue AI, @steadwing, Better Stack and Kagent + an open source only filter!
Check it out here: aisrewatchlist.vercel.app/
Dev Khant retweeted
>compacting day 1 at the @daytonaio compute
>init beautiful SF day
Catch us at the expo hall at Chase Center in SF today and tomorrow for the @daytonaio Compute Conference.


































