Syed Husnain Khalid@husnain_khalid912
3
Events attended
2
Submissions made
Pakistan
1 year of experience
About me
I am a Cloud Native and AI Engineer with over a year of experience in building AI-powered applications. I specialize in creating production-ready AI agents, handling both UI/UX and backend integration. My expertise includes developing intelligent agents using LangGraph and CrewAI, ensuring scalability and efficiency in real-world applications.
🤓 Latest Submissions
AyeOps: voice-authorized incident command
AyeOps is a voice incident commander. It pages you when production breaks, diagnoses the fault on its own, and then refuses to change anything until a human authorizes it out loud. When a service fails it queries health, tails error logs and finds the deploy that did it, down to the commit and the line that crashes. Then it stops. It proposes a fix, and the relay generates a one-time code that appears only on the operator's screen. The model is never given that code. To authorize, the operator says the action, the service and the code together: "Roll back auth-service, Hotel Alpha." A code on its own is refused, because reading two words off a screen is not the same as understanding the change. The relay checks the readback and runs the change. The model never does. The claim is checkable. The repository ships a checker that reads AssemblyAI's own record of every session, searching system prompts, tool schemas, tool calls and results and every agent turn for the code the operator spoke. Its first run found a real leak: a post-incident summary quoted a spent code. We fixed it and kept the failing test. Since then, 6 sessions and 100 turns searched, 0 occurrences. Built on the AssemblyAI Voice Agent API: speech, model and voice over one WebSocket, JSON-schema tool calling in hold mode, tools that do not exist in the model's schema until there is something to fix, barge-in, session resume, and keyterm prompting so code words transcribe correctly the first time. Nothing in the demo is simulated. Every session gets three real Docker containers that genuinely crash-loop and genuinely recover. Every authorization ships with a recording, a turn timeline and a postmortem: the audit evidence a security review needs before it will let an autonomous agent touch production. Try it with no microphone and no signup: https://ayeops.vexralabs.com
30 Sep 2026
Relocate: IBM Bob heals broken tests, with proof
The problem. Every UI redesign breaks end-to-end tests that were never wrong: a renamed test id, a reworded label, a new wrapper div, a CSS-module hash that changed on the last build. At Google, 16% of tests show some flakiness, and 84% of pass-to-fail transitions were flaky tests rather than real bugs (Google Testing Blog, 2016). Teams re-run, skip or delete the test, and the check quietly disappears. Missing checks are expensive: CrowdStrike's own root-cause analysis of its 2024 outage names "the lack of a specific test". Asking an AI agent to "fix the failing tests" is not safe either. We ran plain IBM Bob six times on the same redesign. In one run it decided "the tests are the source of truth" and reverted the redesign in the app. In all three React runs it fixed a duplicate row by position ("the second list item"), which clicks the wrong person as soon as the list changes. The solution. Relocate heals stale Playwright locators and proves every fix. For each failing test it: 1. captures the page exactly as it was at the moment of failure; 2. maps every interactive element with ZeroDOM, which gives each one a collision-free handle and a selector that matches exactly one element; 3. picks the element the test meant (test title, the assertion after the failing line, row text), writes the locator in the test's own style (getByRole, getByTestId, or a row filtered by name), patches only that one line, re-runs the test, and ships before/after screenshots, a receipt and a pull request. Who uses it, and how. QA and front-end teams with Playwright suites, through three entry points: - IBM Bob IDE, "Relocate Healer" mode: one prompt; Bob spawns one subagent per failure, all in parallel, and each explains its pick. - One command: npm run heal. - A GitHub Action: when a redesign PR turns E2E red, Relocate opens a heal PR into that branch. Results. Bob healed 12/12 stale tests across a static site and a React app (CSS-module hashes, translations, composed test ids, three identical Edit rows): 12 subagents spawned in one turn, 1.74 Bobcoins, zero assertions changed, zero positional or build-hash selectors (PR #1). On a new redesign Relocate had never seen (PR #2), the Action opened the healed PR #3 73 seconds later: 4/4 healed, full suite green. Why it's new. Runtime self-healing tools hide the drift with fallbacks at run time; Relocate fixes the source and ships a reviewable PR. LLM selector guessing can confidently click the wrong element; Relocate only chooses among verified handles that match exactly one element. And unlike a general coding agent, it is checkable: only the locator line can change (any other patch is rejected), Bob cannot write to test files in this mode, and a fix that does not pass is undone. Heal the locator. Never the check.
27 Sep 2026
