Cody tracking issue 2023-04-03–2023-04-17

[beyang]

Plan

Early user feedback has indicated the following are important:

• improved context quality (context quality almost always dictates the accuracy of the Cody response).
• some also prefer a less chat-y, more code-search-y interface
• would like an easy way to insert a generated snippet of code into the right place
• fast autocomplete, triggers automatically
• VS Code is shipping new native plugin endpoints for an upcoming version of GitHub Copilot. We are investigating whether they are willing to open these up.

We also think it would help drive awareness if Cody lived in a separate repository that was completely open source.

Features

Preview Give feedback

1. Cody: completions sourcegraph#50448
   cody feature +2
   
2. Code editing/Cody-in-place sourcegraph#50281
   cody cody/vscode +2
   
3. Improve UI of VSCode Extension sourcegraph#50344
   cody cody/vscode +2
   
4. get weaviate running inside App and compare with current approach (Recall, latency, MEM). sourcegraph#50507
   +0
   

Bugs and other stuff

Preview Give feedback

1. Cody: local keyword context is broken sourcegraph#50446
   bug cody +2
   
2. Cody: Fix context fetching issues sourcegraph#50462
   bug cody cody/context testing +4
   
3. Cody chat input doesn't work with Japanese/input method editor (IME) languages sourcegraph#50445
   cody cody/core-app cody/vscode +3
   

Next cycle wishlist

Preview Give feedback

1. Pull Cody out into separate OSS repo sourcegraph#50459
   cody +1
   
2. Investigate using a customer's own LLM (chatGPT) contract sourcegraph#50273
   cody cody/admin +2
   
3. Abuse detection + blocking mechanism
4. Factor out stuff in Go binary
5. Toggle LLM backend endpoint, need to support both OpenAI and Anthropic, $CUSTOMER wants it
6. Onboarding papercuts sourcegraph#50713
   cody +1
   
7. Self-hosted embeddings

[jdorfman]

@beyang done and more coming daily

[malomarrec]

@beyang who's working on the VS Code extension issue? Looks unassigned?
I'd like to bump https://github.com/sourcegraph/sourcegraph/issues/50180

[beyang]

@malomarrec no one AFAIK, want to bring it up on Monday's sync?

[malomarrec]

@sourcegraph/cody shall we have a recorded Cody demo at the end of this sprint, to share progress with others?

[malomarrec]

@sourcegraph/cody shall we close this?