Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Great to hear you're getting a ton of value out of it!
On the annoying parts, yeah, we want to improve these.
Overly positive English prose in Markdown is probably a function of the underlying LLM in use (Claude/GPT-4, plus experimental support for others). I guess the risk is that we overcorrect too far and suddenly the Markdown suggestions are off-putting. If you have any specific examples you'd feel comfortable posting to https://github.com/sourcegraph/cody/discussions/358, that would be helpful.
On inline suggestions (autocomplete), we are under much tighter latency constraints than for chat or commands, so the context used for autocomplete is lighter right now. This is a huge area of effort for us, and we're watching completion acceptance rate really closely. We are making autocomplete use embeddings for context in more cases, and @beyang is adding a fast local context search path as well.
On the VS Code extension APIs used, yes, there are some new proposed APIs that are not yet freely available to extensions that will help. For now, the new `Cody: Fixup` command is much smoother UX than the inline comment `/fix whatever`—give that a try and let us know if that is better.
Thanks!
https://github.com/sourcegraph/zoekt seems to be doing a fair but of heavy lifting for Cody.
A couple WIP ones: https://github.com/keegancsmith/emacs-cody and https://github.com/j-shilling/lsp-cody. Our head of eng (Steve Yegge) is going to start hacking on one this week, I hear. :)
A couple WIP ones: https://github.com/keegancsmith/emacs-cody and https://github.com/j-shilling/lsp-cody. Our head of eng (Steve Yegge) is going to start hacking on one this week, I hear. :)