This is a fork from the original repo. It seemed to have stopped development. So it is maintained here now.

Things this fork has added:

• Chat
• Support for chat based models (gpt-3.5-turbo, gpt-4)
• Document Q&A (using indexer for handling out-of-context sized content)
• Codebase generation

This uses the value of $OPENAI_API_KEY from the current enviroment. It should be set to your OpenAI API key.

The default model used is gpt-3.5-turbo. Edit this file if you want to use something else:

lua/nvim-magic-openai/init.lua

• Completion
• Docstring
• Alteration
• Chat
• Document Q&A
• Codebase generations

When using chat, the window you focus on when you start the chat will be selected for the rest of the session. Until Neovim is closed or until you manually reset the chat (mcc). If text is selected in the visual, this information is passed along with the query but hidden from the chat window. See the demo gif below.

You'll want to double check the code, but this should be enough to get you started on your project.

Ask questions about documents of any size. You need to set up a chat window beforehand. The cursor needs to be in the document that you want to ask questions about.

• latest stable version of Neovim (nightly may work as well)
• curl
• OpenAI API key

-- using packer.nvim
use({
	'ricardicus/nvim-magic',
	config = function()
		require('nvim-magic').setup()
	end,
	requires = {
		'nvim-lua/plenary.nvim',
		'MunifTanjim/nui.nvim'
	}
})

See docs/config.md if you want to override the default configuration e.g. to turn off the default keymaps, or use a different OpenAI model (defaults to gpt-3.5-turbo).

Your API key should be made available to your Neovim session in an environment variable OPENAI_API_KEY. See docs/openai.md for more details. Note that API calls may be charged for by OpenAI depending on the model used.

 export OPENAI_API_KEY='your-api-key-here'

These flows have keymaps set by default for visual mode selections (though you can disable this by passing use_default_keymap = false in the setup config).

You can map your own key sequences to the predefined <Plug>s if you don't want to use the default keymaps.

There is a development container specified under the .devcontainer directory, that builds and installs the latest stable version of Neovim, and sets it up to use the local nvim-magic repo as a plugin.