The focuses of August and September were all about taking our Chat experience to the next level.
In case you missed it, here are a bunch of improvements we made to Chat:
The biggest highlight was obviously bringing the Chat experience to all JetBrains IDEs. What may be less visible is the tons of backend work to unify a lot of how the VS Code and JetBrains Chat experiences operate. This is important because it will allow us to much more rapidly bring Chat to all of our other IDEs (and propagate any future changes). Speaking of changes…
@ search and tag functions
A lot of users love the “code lens” buttons that appear above functions to take an action on that function, but many users pointed out that they often just want to refer to this function as context in a Chat question, perhaps because they think it would be helpful background information or because there are simply multiple functions to synthesize. Now, you can use @ search to pull these functions into your Chats!
Separate chat histories per VS Code workspace
Before, users would complain that the chat history would persist even if they open up a new workspace. In VS Code, this is fixed, where there is a separate history per workspace! Now you can switch workspaces and be able to seamlessly jump right back into where you left off.
Multi-window Codeium Chat in VS Code
On the topic of separate histories, we have also enabled multi-window Codeium Chat in VS Code. Have a few different threads of thought going on in parallel? No problem, just open up another window!
Insert into terminal
One of the surprising things about our Chat system is that it can produce terminal commands if asked. In VS Code, we’ve hooked up Chat to the terminal so you can pass the command to the terminal at a click of a button, rather than having to copy-paste. We are constantly trying to make the AI integration points smoother and more intuitive!
Improved markdown handling
Users love the code blocks produced in Chat responses, and the ability to copy or insert them, but there were a lot of reports of badly formatted code blocks due to poor markdown handling. We made sure to improve our formatting greatly, so now Chat results are properly formatted for arbitrary markdown, such as inline variable/method names.
Of course even more is coming for Chat, but there have been other improvements across the board:
More features ported to Enterprise customers
Our self-hosted enterprise customers now have access to our new proprietary Chat model to run self-hosted Chat, which has been a huge undertaking to train our model from scratch. Also, self-hosted users now have access to a bunch more IDEs such as Eclipse, XCode, and Visual Studio.
New share dropdown on the profile page
One of our most common types of emails we receive is along the lines of “thank you for providing this for free, how can I support you?” Our answer is always that the best way to help us is to share your Codeium experience with your developer friends, slacks, discords, or other communities. To make this easier, we created a new share dropdown on your profile page. Please check in on this dropdown when you view your analytics for new ways to share Codeium (there may or may not also be exclusive offers and perks there in the future…).
Built with Codeium readme badge
One of the new methods of sharing Codeium in this new share dropdown is a “Built with Codeium” README badge that anyone can use to add to the documentation of their repositories. This is the easiest way to passively let other developers know about Codeium.
We would greatly appreciate if you take one minute to add the badge to your repositories’ READMEs:
[![built with Codeium](https://codeium.com/badges/main)](https://codeium.com)
We are now up to many hundreds of thousands of developers on the platform. Thank you for your continued support and we look forward to closing out the year on a high note!