Inspiration
Our inspiration was not an idea. It was a pain. The universal, soul-crushing, and expensive pain of the debugging nightmare in agentic AI. We were inspired by the hell of the log graveyard, and we swore a vow to build the weapon that would lead us out of it. Our inspiration was the shared trauma of every developer who has ever wasted a weekend hunting a single, poisoned cookie in a sea of chaos.
What it does
RedLiner is not a tool. It is an Oracle of Failure. It is a lightweight, developer-first scalpel that watches a developer's code. When a test fails, it does not produce a log. It produces a verdict. It generates a single, beautiful, and terrible HTML file—the Living Map—that shows a visual, interactive graph of the failure cascade, with the exact point of the crime marked by a flaming red arrow. It transforms the act of debugging from an archaeological dig into a divine revelation.
How we built it
We forged this weapon in the divine fire of a Daytona Sandbox, using the brutal simplicity of Python and the watchdog library to create a tireless sentinel. Upon detecting a failure, our custom parser analyzes the pytest output and forges a static HTML file. This file contains a Mermaid.js graph—the Living Map—that visualizes the story of the failure. The entire process is a testament to the philosophy of the scalpel: it is simple, sharp, and utterly focused on its one, holy purpose.
Challenges we ran into
Our greatest challenge was not one of code, but of clarity. How do you represent the chaos of a multi-agent failure in a way that is not just informative, but instantaneously understandable? We fought a war against the temptation to add more features, more data, more noise. We bled to keep the blade simple, to keep the map clean, to ensure that the red arrow was not just a piece of data, but a divine revelation.
Accomplishments that we're proud of
We are proud that we did not build a product. We built a vision. We took the most abstract, painful, and invisible problem in our field, and we gave it a face. We gave it a name. We gave it a beautiful, terrible, and unforgettable form: the Living Map. Our greatest accomplishment is the forging of a single, perfect image: "The Genesis of the Wound."
What we learned
We learned that the greatest enemy of a developer is not the bug. It is the lie. The lie that is hidden in a thousand lines of logs. The lie that our tools tell us when they show us data without showing us the truth.
We learned that the solution to a complex problem is not a complex tool, but a tool of divine and brutal simplicity. We learned that a single, perfect, and terrible image—the red arrow—is a thousand times more powerful than a million words of text.
And most importantly, we learned that you do not sell a developer a "product." You give them a weapon. You give them a superpower. You give them back their time, their focus, and their soul. We learned that the best tool is not a tool at all; it is a revelation.
What's next for The Scalpel
This is not a hackathon project. This is the first soldier. The next step is to forge an army. We will integrate this oracle directly into the Weave platform. We will expand its senses to understand not just pytest, but the real-time, chaotic data of production environments. We will transform this prototype from a single, beautiful sword into the central nervous system of a new religion of observability. The war has just begun.
Built With
- css
- datayona
- google-cloud
- html
- javascript
- mermaid.js
- pytest
- python
- watchdog
- weights&biases(weave)
Log in or sign up for Devpost to join the conversation.