cody

Cody is open source: https://github.com/sourcegraph/cody. And for the reasons explained there, it makes more sense for it to be open source.

Yes, Cody can use Ollama for both chat and autocomplete. See https://sourcegraph.com/docs/cody/clients/install-vscode#sup.... This lets you use Cody fully offline, but it doesn't /prevent/ API calls to third parties; you are still able to select online models like Claude 3.5 Sonnet. I have a WIP PR right now (like literally coding on it right now) making Cody support strict offline mode better (i.e., not even showing online models if you choose to be offline): https://github.com/sourcegraph/cody/pull/5221.

Sourcegraph CEO here. We made our main internal codebase (for our code search product) private. We did this to focus. It added a lot of extra work and risk to have stuff be open source and public. We gotta stay focused on building a great code search/intelligence product for our customers. That's what ultimately lets us still do plenty of things for devs and the OSS community: (1) Our super popular public code search is at https://sourcegraph.com/search, which is the same product customers use internally on their own codebases. We spend millions of dollars annually on this public instance with almost 1M OSS repositories to help out everyone using OSS (and we love when they like it so much they bring it into their company :-). (2) We also have still have a ton of open-source code, like https://sourcegraph.com/github.com/sourcegraph/cody (o

Yeah, 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 2. (experimental) TypeScript tsc context — https://github.com/sourcegraph/cody/pull/3843 3. (experimental) OpenCtx, which can pull in diagnostics from tools outside your editor — 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.

Awesome to see our Rust fine-tune here on HN. We (Sourcegraph team) are here if anyone has questions or ideas for us! BTW, Cody is open source (Apache 2): https://github.com/sourcegraph/cody.

checkout the cody extension https://github.com/sourcegraph/cody available for various editors like vscode

I don't think it is. There is a test file which includes C#, Kotlin, etc among supported languages, and those aren't included in the file you linked: https://github.com/sourcegraph/cody/blob/main/vscode/src/com... But this test didn't seem to include TypeScript so it's obviously not comprehensive. I'm not convinced this information is actually in one place.

This should be the correct link: https://github.com/sourcegraph/cody/blob/main/vscode/src/gra...

> Because of the language-specific nature of this heuristic, we generally do not support multi-line completions for all languages. However, we’re always happy to extend our list of supported languages and, since Cody is open-source, you can also contribute and improve the list. (link to https://github.com/sourcegraph/cody/blob/main/vscode/src/com...) That link to the list of supported languages is broken. I couldn't find a similar file elsewhere in the repo: maybe the list got folded up into a function in another file? Also a bit annoying that I couldn't find the info on the company's website (though I gave up pretty quickly).

Cody (https://github.com/sourcegraph/cody) supports using Ollama for autocomplete in VS Code. See the release notes at https://sourcegraph.com/blog/cody-vscode-1.1.0-release for instructions. And soon it'll support Ollama for chat/refactoring as well (https://twitter.com/sqs/status/1750045006382162346/video/1). Disclaimer: I work on Cody and hacked on this feature.

You can try it with Sourcegraph Cody. https://sourcegraph.com/cody And instructions on how to change the provider to use Ollama w/ whatever model you want: Install and run Ollama - Put ollama in your $PATH. E.g. ln -s ./ollama /usr/local/bin/ollama. - Download Code Llama 70b: ollama pull codellama:70b - Update Cody's VS Code settings to use the unstable-ollama autocomplete provider. - Confirm Cody uses Ollama by looking at the Cody output channel or the autocomplete trace view (in the command palette). - Update the cody settings to use "codellama:70b" as the ollama model https://github.com/sourcegraph/cody/pull/2635

I'm sorry to hear that. We have made a lot of improvements to Cody recently. We had a big release on Oct 4 that significantly decreased latency while improving completion quality. You can read all about it here: https://about.sourcegraph.com/blog/feature-release-october-2... We love feedback and ideas as well, and like I said are constantly iterating on the UI to improve it. I'm actually wrapping up a blog post on how to better leverage Cody w/ VS Studio, that'll be out either later today or sometime tomorrow. As far as feedback though: https://github.com/sourcegraph/cody/discussions/new?category... would be the place to share ideas :)

Ollama is awesome. I am part of a team building a code AI application[1], and we want to give devs the option to run it locally instead of only supporting external LLMs from Anthropic, OpenAI, etc. Those big remote LLMs are incredibly powerful and probably the right choice for most devs, but it's good for devs to have a local option as well—for security, privacy, cost, latency, simplicity, freedom, etc. As an app dev, we have 2 choices: (1) Build our own support for LLMs, GPU/CPU execution, model downloading, inference optimizations, etc. (2) Just tell users "run Ollama" and have our app hit the Ollama API on localhost (or shell out to `ollama`). Obviously choice 2 is much, much simpler. There are some things in the middle, like less polished wrappers around llama.cpp, but Ollama is the only thing that 100% of people I've told about have

Are you sure you're not thinking of Cody the tool? https://github.com/sourcegraph/cody The names are very similar.