[milani]

In my experience working with GPT4, if I give enough context on types, other functions definitions and the libraries I use, I get very accurate results. But it is a tedious task to copy paste from multiple places (type definitions, function definitions, packages, etc.).

In addition to the selected lines, does Continue support getting related definitions from the language server and inject them in the prompt? That would be huge.

[sestinj]

This is very near on the roadmap, and we agree it will be awesome!

As of now, if there are collections of definitions that you frequently reference, you could save them in the system message, or write custom slash commands that let you prefix your prompt with these definitions.

[Aperocky]

> if I give enough context on types, other functions definitions and the libraries I use, I get very accurate results.

It's almost like .. coding it yourself!

[thumbuddy]

After I copy every piece of code that is relevant, ask it to do something, then correct it's errors using human knowledge, then ask senior devs if it makes sense to revise my prompts and repeat, fix bugs from reviews from other humans, it's like this magical thing I get the mostly right answer!

[milani]

For smaller pieces, you are right. But as a BE engineer, I was prototyping a concept and I didn't know much about Typescript+React+React-Router-Dom+React-Hooks-Form, etc etc. So I listed the libraries, a few lines of boilerplate and API definitions that RTK toolkit generated for me. Then asked GPT to generate the full page. It was much faster than I could "code it myself".

And that's why it is a "pain point". These all can be done automatically.

[johnfn]

And driving to the store is basically just like walking there yourself!

[lalwanivikas]

I have been experimenting a lot lately, and I would much rather copy paste high quality output(via providing context) than playing guessing games.

It's not like you have to be coding all the time.

Things will of course change as tools evolve.

[sestinj]

Couldn't agree more—it's worth the extra effort to know exactly what enters the prompt. But control isn't mutually exclusive with removing the need to copy/paste. Continue lets you highlight code with perfect precision, and this is much lower effort.

[milani]

I'd say it is a UX concern. It could show you the things it referenced in the prompt. So you'd only hit enter or customize it if needed :shrug:.

[bvm]

I also found this tedious and made a tiny vscode extension to make it less tedious

https://marketplace.visualstudio.com/items?itemName=TomJenni...