The next two languages are Go and Ruby as it happens! We need to make some changes based on learnings from the launch today first but it’s relatively easy for us to implement these new languages

Thanks! It’s much harder to implement that’s for sure but I totally agree that it’s a great way to interact, being able to and follow up messages and clarify things is really great

Thanks for flagging - will get this fixed! For reference the paper is here: https://arxiv.org/abs/2212.10496

Thank you very much! Released an article yesterday on my tips for the ChatGPT API if you haven’t already seen it!

Not currently, I think jetbrains is definitely next in terms of priority but I think as per some suggestions on here and on Twitter we may end up releasing our headless API to allow people to build their own integrations - need to hire some more devs first though!

Would love this as I know Emacs people would build a package in an instant given an accessible API.

I’ve heard a few reports of slow indexing, it may be load related but I need to investigate further (on a flight currently so will look when I land), if you’re happy to drop me a line on [email protected] and I’ll try to help figure this out!

This may be load related - very happy to provide support on your issue if you can drop me a line at [email protected]

Interesting suggestion, the extension itself is actually a React project that runs in VS Code so not much uplift would be required but we’d have to figure out how we’d actually interact with the codebase in that instance

github oauth?

How would this work with local changes while developing?

Hey, thank you for the feedback - are you unable to get beyond the sign in point? If you could drop me a line on [email protected] I’ll gladly try to sort this out for you!

Yes we do in the medium term, we fortunately built the product in a modular/headless way so adding further integrations is easier, although we're strapped for dev resource currently so once that problem is alleviated then we can start looking at supporting more IDEs!

If it is headless , I assume that their is an API that you could maybe release to the public so companies could build their own IDE plugins or even integrate it further into their workflow like adding code fractions automatically to tickets etc.

Yes we’ve definitely considered this as an option, we’ll hopefully be able to explore it more when we have more dev resource in the next few months (just my cofounder and I working on the tech currently). I think it makes a lot of sense to allow people to make their own integrations!