4 ms·
I have to admit. This is marketing done right. Same as the retool post. Also, in the next few years all the sauce and moat of these kinds of systems will be in
by lysecret 3y ago
I have to admit. This is marketing done right. Same as the retool post.
Also, in the next few years all the sauce and moat of these kinds of systems will be in the retrieval architecture. I wish they would go into further detail (just a little bit at then end).
In any case great read! Might even give it a try.
- intrepidsoldier 3y agoDetails were left for the actual announcement blog post - https://sourcegraph.com/blog/cody-is-generally-available https://sourcegraph.com/blog/cody-is-generally-available Disclaimer: I work for Sourcegraph.
- imjonse 3y agoEven though 'context' is mentioned many times in that post, I am still unsure if the power of Cody comes only if you import your repo in sourcegraph. It does not seem like using it within VSCode in your local source directory lets is understand and use everything there, but I am happy to be corrected.
- intrepidsoldier 3y agoAlmost every example mentioned in that announcement blog post I linked above is that of Cody working with local files in VSCode.
- imjonse 3y agoOf course it is working with local files, maybe I phrased it awkwardly. I am just not sure whether it gives you full context if you do that. I have used Cody a few times in the past few months and it's good, but at least its chat feature kept saying it does not have access to the local code. Maybe that's Claude/GPT being honest but when and which local files it picked seemed unpredictable. There's a setting whether you want sourcegraph context or local context only, and from one of the previous announcements I understood it can work with public github repos. Hence my confusion whether it truly and fully can use your local folder by scanning it locally and extracting embeddings or you need it to go through sourcegraph to get the most out of it.
- intended 3y agoIs whoever wrote that post, specifically, hiring?