| ▲ | tcdent 2 hours ago | |
Agents wrote the code, agents tested the code, agents reviewed the diff, a human reviewed the diff, agents verified it made it to production correctly. But when the pipeline fails (bugs happen that's fine) re-running the exact same process may not be the solution. Where does the additional intelligence that wasn't there before come from? We ran the pipeline that got it to prod on the same exact models you have access to. So the value prop is that you read the logs automatically instead of a developer directing a debug session? | ||
| ▲ | karanraina 2 hours ago | parent [-] | |
the value prop is not reading logs automatically your coding agent will have access to your code and can see what logs you have enabled, if indeed that would help in debugging, going that route helps. it can take your agents a bunch of retries but it might get there if the answer is in logs what we provide your coding agent is a detailed snapshot of all your variables at any line it feels would help debugging. and not just in the current call frame.. even the variables of the callers of your current function, like a debugger. suupose funcA() -> funcB() -> funcC() -> yourCurrentFn() we'll provide all the variables that were set in all 4 functions to your agent. debugging using this would be a lot more accurate and you just one snapshot like this instead of looking at a thousand log lines to understand why something is not working the way you want to. this kind of data is missing from your logs and and even your traces because it will be impractical for privacy and performance. | ||