CodeContinue: LLM powered code completion tool

[kXborg]

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is codeContinue.

• It's build to provide LLM powered code completion.
• Just start with 1-2 line of comments and continue coding, it suggest next line of code instantly
• Use any OpenAI compatible endpoint to serve a model and use the same here. I use Qwen2.5-Coder-1.5B-Instruct on a jetson orin nano from vLLM. It works decent.
• The goal is to have control over the models we use, and keep data local.

Disclaimer: I am aware of potential key binding conflicts, however Tab key rarely will be creating issue. Also it is only triggered when suggested code phantom appears while coding. We have tested it rigorously, and we beleive it should not create issues. Having said that, the instructions have been added to change it in the first run -- in case any conflicts exists. I hope the package will not be declined.

There are no packages like it in Package Control.

*) If you do need a context menu, make sure the menu applies to the cursor
context, and the commands are conditional. Space in this menu is limited!
**) There aren't enough keys for all packages, so you risk overriding those
of other packages. You can put commented out suggestions in a keymap file,
and/or explain how to create bindings in your README.
***) Syntaxes should work in any color scheme the user chooses.

For bonus points also consider how the review guidelines apply to your package:
https://docs.sublimetext.io/reference/package-control/reviewing.html