Viewing profile — kirtivr

Congratulations on the launch. I love the idea and the execution. When I looked into this a while back I explored using ptrace() to add breakpoints and even add functions at specif…

Deepseek has always been better than people gave it credit for. You have to be careful with the inference provider though, Chinese providers are subject to laws that mandate data s…

One big reason I can think of is to avoid vendor lock-in. This is why most enterprises use a multi-cloud setup, despite the increased complexity.

Here is a counterexample to whatever counterexample you have in mind - Most popular models on OpenRouter right now: https://openrouter.ai/models?categories=programming&order=mo... …

FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self-hosted …

to be fair, coding agent harnesses have been becoming more and more complex. it's not an llm in a loop with tools anymore (as claude code was rumoured to be on HN).

A few different ways: - Copilot may be better at implementing features. We're better at investigating bugs and fixing them. - We handle huge context very easily. We specialize towa…

This is on our roadmap! At this time we are focussing on evaluation benchmarks like SWE-bench (verified). This is a simpler benchmark and does not really map well to investigating …

Thank you! are you using any AI tools to debug productions issues at this time? Would love to have you join our Discord- https://discord.gg/XNXVD34P8

Hey satyamtiwary thanks so much for trying the product! We'd love to have you join our Discord: https://discord.gg/XNXVD34P8

Thanks. As teams move faster with AI generated code, the focus on quality and reliability will have to increase as well. And we will have to build better tools if we want to accele…

Thank you! are you using any AI tools to debug productions bugs at this time?

Nginx, Caddy, Flink and Firefox are some applications where we we've managed to consistently fix and reproduce reported bugs. Of course, we did not send the PRs to the repos seeing…

We either mock or fake out the interfaces. I much prefer faking to mocking, because that still preserves a lot of the real-world behavior relevant to prod bugs. A full prod reprodu…

War story time? xD

On how does the mocking work, that's a really interesting question. We do a lot of AST parsing - for both code and build configuration languages. Even then, we still have to rely o…

It's really nice to hear that. FixBugs was built because while investigating prod incidents, I had an epiphany. SWEs build tools to solve all types of problems, but we ourselves us…

On Linux, we rely on a chroot-ed workspace at this time - although we are working on a prototype using the new landlock kernel interface ( https://github.com/Zouuup/landrun ). OSX …

Thank you so much. are you using any AI tools to debug productions issues at this time?

Thank you so much. are you using any AI tools to debug productions issues at this time?

Oh the repro runs in an isolated sandbox, and all interactions outside the sandbox (with lets say other services or databases) are mocked. The repro harness doesn't have access out…

Thanks a lot! I think FixBugs is most useful during high volume bug triage. This is where having a low false-positive async debugging agent is most helpful.

A different approach that we took to root causing bugs that you may find interesting is that we first try to reproduce the bug before coming up with a fix for it. This is essential…

I built FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self…