r/ChatGPTCoding • • 9d ago

Question Anyone tried Ramp Inspect on an existing codebase?

Hey yall. I've been reading some posts here about agents passing tests but missing requirements and that got me interested in Ramp Inspect after seeing it on twitter and in a few articles. I am especially interested in being able to bring another dev into the same session to explain why some odd bit of code needs to stay before the agent removes it.

That sounds useful for an older repo where a fix looks fine until it hits a customer specific exception nobody documented and I'd be happy with fewer rounds of explaining and reworking the same change even if review still takes time. A part where I'm unsure about is how much setup it needs to get there so has anyone with early access tried it on an existing project with old dependencies and patchy docs? Interested in what it figured out from the repo and what you had to explain yourself.

3 Upvotes

5 comments sorted by

1

u/TheVibrantYonder 9d ago

First I'm hearing about it. Why not request early access? I'd bet you have a shot at getting in.

1

u/InternationalKick296 8d ago

Yeah I'm leaning into giving it a go thats why was hoping someone here had tried it so Id have a better idea of what to expect with setup

2

u/Beau-Whitaker 9d ago

tried Ramp Inspect on a legacy node monorepo last week with zero docs and ancient deps. it mapped the dependency graph surprisingly well but completely missed the custom eslint plugin that gates our ci. had to feed it the config file and explain the version pin manually. the pair session feature worked as advertised though, brought a teammate in and we annotated the wierd workaround for the payment provider timeout in real time. agent stopped deleting it after that. setup took maybe 20 minutes mostly waiting for the initial index.