3 ms·
I’ve been using Cody and liking it, but one thing I noticed is there is no loop that even takes the data from the IDE and incorporates the IDE’s feedback into t
by MarkMarine 2y ago
I’ve been using Cody and liking it, but one thing I noticed is there is no loop that even takes the data from the IDE and incorporates the IDE’s feedback into the code it generates. It’ll happily generate code the IDE draws red wiggle lines under and just continue on with its day. Would be nice to see a tighter integration
- sqs 2y agoYeah, that is needed to make everything more accurate. We are working on 3 related things to make Cody better understand the structure of your code and take feedback from the compiler (and other tools). All are experimental and not enabled by default, but you can peek at them if you're interested. 1. (experimental) LSP-based context — https://github.com/sourcegraph/cody/pull/3493 https://github.com/sourcegraph/cody/pull/3493 2. (experimental) TypeScript tsc context — https://github.com/sourcegraph/cody/pull/3843 https://github.com/sourcegraph/cody/pull/3843 3. (experimental) OpenCtx, which can pull in diagnostics from tools outside your editor — https://openctx.org/ https://openctx.org/ And then of course the agent to actually iterate on the generated code based on this feedback. We're really excited about this stuff, and it'll arrive in Cody when we can get it to a high quality bar and prove it helps.
- MarkMarine 2y agoAwesome! I’ll take a look