beyang

If you like Claude Code but either (1) prefer an agent that doesn't ask for review on each file edit or (2) miss the IDE for things like reviewing diffs, I'd humbly submit you try out Amp: https://ampcode.com. It has both a CLI and VS Code extension, and we built it from the ground up for agentic coding, so no asking for permission on each edit, a first-class editor extension (personally I spend more and more time reviewing diffs and VS Code's diff view is great), and it employs subagents for codebase search and extended thinking (using a combo of Sonnet and o3) to maximize use of the context window.

Check out Cody for GoLand and JetBrains: https://plugins.jetbrains.com/plugin/9682-cody-ai-coding-ass...

For those looking for a free coding assistant they can also use at work / in the enterprise, Cody has had a free tier for awhile: https://sourcegraph.com/cody

- Works with local models

- Context-aware chat with very nice ergonomics (we see consistently more chats per day than other coding assistants)

- Used by both indie devs and devs at very large enterprises like Palo Alto Networks

- Hooks nicely into code search, which is important for building a strong mental model inside large, messy codebases

- Open source core

FYI, you can do that with Cody + Ollama. A good portion of our user community does exactly that: https://sourcegraph.com/blog/local-code-completion-with-olla...

Hi there, Cody contributor here—sorry to hear you had a bad experience! In our evals, our DeepSeek variant outperformed previous models and other alternatives. If it's working worse for you know, would be open to sending us some examples/screenshots of poor completions examples? We'd like to incorporate these into our eval set so we can capture a more representative distribution of codebases and how Cody performs!

This is in the cards and thank you for the feedback! (Sourcegraph CTO here)

Author of the post here—as another commenter mentioned, this is indeed a bit dated now, someone should probably write an updated post!

There's been a ton of evolution in dev tools in the past 3 years with some old workhorses retiring (RIP Phabricator) and new ones (like Graphite, which is awesome) emerging... and of course AI-AI-AI. LLMs have created some great new tools for the developer inner loop—that's probably the most glaring omission here. If I were to include that category today, it would mention tools like ChatGPT, GH Copilot, Cursor, and our own Sourcegraph Cody (https://cody.dev). I'm told that Google has internal AI dev tools now that generate more code than humans.

Excited to see what changes the next 3 years bring—the pace of innovation is only accelerating!

If folks want to continue searching open source, https://sourcegraph.com/search does not require sign in and also includes major projects that are not on GitHub.

(Full disclosure: I'm the Sourcegraph CTO)

Zoekt was heavily inspired by Google's internal code search, as mentioned in the blog post. The original version of the internal code search is described in the rsc post. Zoekt keeps some of the foundational ideas (e.g., trigram index), but was a from-scratch implementation. We probably should link to the rsc post for completeness, will update.

Great call out! We've built this code navigation infra on top of Zoekt into Sourcegraph. Example: https://sourcegraph.com/github.com/golang/go/-/blob/src/net/...

Docs: https://docs.sourcegraph.com/code_navigation/explanations/pr...

This was a great listen that really resonated with the approach we've taken in building our code AI tool (Sourcegraph's Cody: https://cody.dev). We found that the biggest levers we had to drive improvement in the accuracy of Q&A and code generation quality was fetching relevant snippets of code and docs into the context window. So we pivoted from investigating more expensive, long-iteration-cycle updates at the model training level and invested more into code-specific information retrieval mechanisms (it helps that we spent the past 10 years building a code search and code intelligence engine). We've found RAG to be cheap, fast, and directly impactful compared to model-layer improvements (but as Jerry points out, still a very hard engineering problem).

Anyway, Jerry and LlamaIndex has been a huge source of learning and inspiration—please keep tweeting and publishing, Jerry!

Hello, Sourcegrapher here! We are making some simplifications to eliminate the need for the separate local app install. Should be out in the next month or so. Until then, apologies for the added friction here, we're working hard to smooth it out.

Hi there, Sourcegraph CTO here. Code search remains free for individual devs, and I hope you'll continue using us for your projects! https://about.sourcegraph.com/code-search/pricing

We have lots to reflect on given the feedback here on HN. We were honestly a bit blindsided by the number of people who appear to be using open source Sourcegraph, or who really wanted to use it but found the process too difficult. Part of this is because we had a zero telemetry policy for the open source distribution. Perhaps that was a mistake in hindsight, but introducing telemetry there would've been another can of worms!

Now that the usage is more visible, it's actually kicked off a lively internal discussion. We're going to take some time to gauge the size of the user community and figure how we can best support it. Aside from individual use being free (still the case) and making deployment more straightforward (through something like code search in App), are there other things we can do to make it easier to adopt? Sorry about the confusion here, we should have handled this better. But the silver lining is we realized there were a lot of users of Sourcegraph that we didn't know about and we're now discussing how best to engage and support you all. I do hope you'll take the chance to pop into our Discord and say hello and continue with feedback that can help us make the best decisions for our users.