RuntimeFix
The debugger-aware bug-fixing agent that actually sees what broke.
Core trick
Captures runtime variable values at the failing stack frame via the debugger and passes them to the model alongside the stacktrace.
Description
The debugger-aware bug-fixing agent that actually sees what broke.
README excerpt
# 🛠️ RuntimeFix
### The debugger-aware bug-fixing agent that actually sees what broke.
---
## 💡 The pitch in one line
> Every AI bug-fix tool reads the **text** of your stacktrace and guesses.
> **RuntimeFix reads the stacktrace *and the actual variable values* at the moment of failure.**
That's the difference between "maybe add a type check?" and a precise,
reproducible fix with a regression test attached.
## 🩸 Why this matters
Debugging is where developer hours go to die. Most production bugs
aren't in the logic you wrote — they're in the *data* you didn't expect.
Polymorphic payloads, schema drift, one poisoned record in a batch of
10,000. The stacktrace points at a line. It does not tell you **which
input shape** caused it.
Every existing AI tool — Sentry Autofix, Junie, Copilot, Cursor — gets
the same information a human gets from `traceback.print_exc()`. They're
all playing the same limited-information game. RuntimeFix changes it. 🎲→🎯
## ⚙️ How it works
```
┌──────────────────────────┐
│ Your Python app 💥 │
└────────────┬─────────────┘
│ raises
▼
┌──────────────────────────┐
│ 📸 Runtime snapshot │ • Walk the traceback
│ │ • Snapshot every frame's locals
│ │ • Type-annotated, bounded serialization
└────────────┬─────────────┘
│
▼
┌──────────────────────────┐
│ 🧠 LLM (any provider) │ Prompt = stacktrace + runtime values +
│