How to set up gp.nvim with Ollama for local AI models?

Configure the Ollama provider in settings with the endpoint http://localhost:11434/v1/chat/completions, ensure the Ollama service is running with models like Llama3, and adjust agents as needed for chat or command tasks.

Can gp.nvim work with GitHub Copilot without extra plugins?

Yes, gp.nvim can access Copilot's GPT-4 model by configuring the copilot provider with your API key, but for autocomplete features, you still need separate plugins like copilot.lua.

What's the difference between gp.nvim and other Neovim AI plugins like codeium.nvim?

Gp.nvim focuses on chat sessions, instructable operations, and multi-provider support, while codeium.nvim is primarily for code autocompletion. Choose based on whether you need conversational AI or just completion assistance.

How to use speech-to-text in gp.nvim on Linux?

Install SoX via your package manager (e.g., apt-get install sox libsox-fmt-mp3 on Ubuntu), then use commands like :GpWhisper to dictate prompts; the plugin handles recording and transcription automatically.

Is gp.nvim suitable for generating code documentation?

Yes, you can create custom hooks for documentation tasks or use :GpRewrite with prompts, and project-specific instructions in .gp.md files help guide the AI for consistent output across files.

How to customize agents in gp.nvim for specific tasks?

Define agents in the config with name, provider, model, and system prompt; for example, disable default agents and add custom ones for chat or command modes, as shown in the providers and agents configuration section.

Does gp.nvim support image generation with DALL-E?

Yes, gp.nvim includes :GpImage for image generation, likely using OpenAI's DALL-E or similar via configured providers, with options to save images to disk after generation.

gp.nvim — AI Chat Plugin for Neovim

What is gp.nvim?

Gp.nvim is a Neovim plugin that integrates GPT models directly into the editor, enabling ChatGPT-like sessions, instructable text and code operations, speech-to-text, and image generation. It extends Neovim's native capabilities with AI features while maintaining a lightweight and extensible design, allowing developers to interact with AI without leaving their editor.

Target Audience

Neovim users, particularly developers and technical writers who want to incorporate AI-assisted coding, documentation, and creative tasks directly within their editor workflow.

Value Proposition

Developers choose Gp.nvim for its minimal dependencies, extensibility via Lua hooks, and multi-provider support including OpenAI, Ollama, Anthropic, and GitHub Copilot. It offers a native Neovim experience with features like streaming responses, undo support, and project-specific custom instructions.

Gp.nvim (GPT prompt) Neovim AI plugin: ChatGPT sessions & Instructable text/code operations & Speech to text [OpenAI, Ollama, Anthropic, ..]

Use Cases

Best For

Conducting persistent ChatGPT-like conversations within Neovim buffers with markdown formatting and autosave.
Performing instructable text and code operations such as rewriting, appending, or prepending content based on user prompts.
Using speech-to-text for dictating prompts, comments, or instructions via voice commands with SoX integration.
Generating images directly from prompts within Neovim, eliminating the need to switch to external tools.
Extending AI functionality with custom Lua hooks for tailored workflows like code reviews, unit test generation, or translations.
Managing multiple AI providers (e.g., OpenAI, Ollama, Anthropic) and switching between agents for different tasks.

Not Ideal For

Teams preferring graphical, IDE-like AI interfaces over command-line text buffers and modal editing
Environments where installing and configuring SoX for speech-to-text is impractical or unsupported
Users seeking out-of-the-box AI autocompletion without additional setup for providers like GitHub Copilot
Projects requiring robust collaborative AI features or integration with non-Neovim tools

Pros & Cons

Pros

Minimal Dependencies

Core functionality relies only on curl and grep, with optional SoX for speech-to-text, reducing plugin conflicts and setup friction as emphasized in the README.

Extensible Hooks System

Lua hooks automatically register as custom commands, allowing tailored workflows like unit test generation or code reviews, demonstrated in the 'Extend functionality' section.

Multi-Provider Flexibility

Supports OpenAI, Ollama, Anthropic, GitHub Copilot, and others via configurable endpoints, offering cost and model choice flexibility without vendor lock-in.

Native Neovim Integration

Uses Neovim buffers for ChatGPT-like sessions with markdown formatting and streaming responses, ensuring seamless undo and editor-native workflows.

Speech-to-Text Efficiency

Integrates SoX for voice commands, enabling faster prompt dictation—claimed to be 2-4x quicker than typing—for tasks like commenting or instruction giving.

Cons

External Tool Dependency

Speech-to-text requires SoX installation, which isn't available on all platforms and adds an extra step, potentially limiting accessibility for some users.

Configuration Complexity

With a 600+ line default config and multiple providers to set up, initial configuration can be daunting and error-prone, especially for API key management.

Limited Ecosystem Integration

Relies solely on Neovim's ecosystem; users wanting AI features across editors or tight integration with other Lua plugins may find it restrictive.

Performance Trade-offs

Uses curl for API calls, which might not optimize latency compared to dedicated libraries, and local models via Ollama can introduce response delays.

Frequently Asked Questions

What is gp.nvim?

Target Audience

Neovim users, particularly developers and technical writers who want to incorporate AI-assisted coding, documentation, and creative tasks directly within their editor workflow.

Value Proposition

Use Cases

Best For

Conducting persistent ChatGPT-like conversations within Neovim buffers with markdown formatting and autosave.
Performing instructable text and code operations such as rewriting, appending, or prepending content based on user prompts.
Using speech-to-text for dictating prompts, comments, or instructions via voice commands with SoX integration.
Generating images directly from prompts within Neovim, eliminating the need to switch to external tools.
Extending AI functionality with custom Lua hooks for tailored workflows like code reviews, unit test generation, or translations.
Managing multiple AI providers (e.g., OpenAI, Ollama, Anthropic) and switching between agents for different tasks.

Not Ideal For

Teams preferring graphical, IDE-like AI interfaces over command-line text buffers and modal editing
Environments where installing and configuring SoX for speech-to-text is impractical or unsupported
Users seeking out-of-the-box AI autocompletion without additional setup for providers like GitHub Copilot
Projects requiring robust collaborative AI features or integration with non-Neovim tools

Pros & Cons

Pros

Minimal Dependencies

Core functionality relies only on curl and grep, with optional SoX for speech-to-text, reducing plugin conflicts and setup friction as emphasized in the README.

Extensible Hooks System

Lua hooks automatically register as custom commands, allowing tailored workflows like unit test generation or code reviews, demonstrated in the 'Extend functionality' section.

Multi-Provider Flexibility

Supports OpenAI, Ollama, Anthropic, GitHub Copilot, and others via configurable endpoints, offering cost and model choice flexibility without vendor lock-in.

Native Neovim Integration

Uses Neovim buffers for ChatGPT-like sessions with markdown formatting and streaming responses, ensuring seamless undo and editor-native workflows.

Speech-to-Text Efficiency

Integrates SoX for voice commands, enabling faster prompt dictation—claimed to be 2-4x quicker than typing—for tasks like commenting or instruction giving.

Cons

External Tool Dependency

Speech-to-text requires SoX installation, which isn't available on all platforms and adds an extra step, potentially limiting accessibility for some users.

Configuration Complexity

With a 600+ line default config and multiple providers to set up, initial configuration can be daunting and error-prone, especially for API key management.

Limited Ecosystem Integration

Relies solely on Neovim's ecosystem; users wanting AI features across editors or tight integration with other Lua plugins may find it restrictive.

Performance Trade-offs

Uses curl for API calls, which might not optimize latency compared to dedicated libraries, and local models via Ollama can introduce response delays.

Frequently Asked Questions

gp.nvim

What is gp.nvim?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

gp.nvim

What is gp.nvim?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?