LSP Support

LSP Support

Codive includes a Language Server Protocol (LSP) implementation that integrates with any LSP-compatible editor. This brings AI-powered coding assistance directly into your editing experience.

Overview

The Codive LSP server provides:

• Code Actions - AI-powered refactoring and code generation
• Inline Completions - Context-aware code suggestions
• Diagnostics - AI-assisted code review and error detection
• Hover Information - Explanations for code under cursor
• Code Lens - Quick actions embedded in your code

Starting the LSP Server

Start Codive in LSP mode:

codive lsp

The server communicates over stdio by default, which is the standard for LSP.

Options

# Use TCP instead of stdio
codive lsp --tcp --port 9257

# Enable verbose logging
codive lsp --log-level debug

# Use specific configuration
codive lsp --config ~/.config/codive/lsp.toml

Features

Code Actions

Codive provides AI-powered code actions through the standard LSP code action interface:

• Explain Code - Get an explanation of the selected code
• Refactor Selection - AI-assisted refactoring
• Generate Tests - Create tests for selected function
• Add Documentation - Generate docstrings/comments
• Fix Issue - Apply AI-suggested fix

In most editors, you can trigger code actions with Ctrl+. or Cmd+..

Inline Completions

Codive provides context-aware completions as you type:

fn calculate_total(items: &[Item]) -> f64 {
    // Type here and Codive suggests the implementation
    items.iter()  // <- Codive completes based on context
}

Note

Inline completions require editor support for textDocument/inlineCompletion (available in VS Code, Neovim with plugins, etc.)

Code Lens

Codive adds actionable hints above functions and classes:

// 📝 Add tests | 📚 Explain | ✨ Optimize
pub fn complex_algorithm(data: &[u8]) -> Result<Output, Error> {
    // ...
}

Click these lenses to trigger the corresponding AI action.

Diagnostics

Codive can analyze your code and provide AI-powered diagnostics:

fn process(data: Option<String>) -> String {
    data.unwrap()  // ⚠️ Codive: Potential panic - consider using unwrap_or_default()
}

Configuration

Configure LSP behavior in codive.toml:

[lsp]
# Enable/disable features
code_actions = true
inline_completion = true
code_lens = true
diagnostics = true

# Completion settings
[lsp.completion]
# Trigger completion automatically
auto_trigger = true
# Delay before triggering (ms)
trigger_delay = 500
# Maximum suggestions
max_suggestions = 5

# Code lens settings
[lsp.code_lens]
# Actions to show
enabled_actions = ["explain", "test", "refactor"]

# Diagnostics settings
[lsp.diagnostics]
# Run on save only (vs. on change)
on_save_only = false
# Severity level
min_severity = "warning"

Protocol Extensions

Codive extends the standard LSP with additional capabilities:

Custom Requests

// Execute a Codive command
interface CodiveExecuteRequest {
    command: string;  // e.g., "explain", "refactor", "test"
    arguments: {
        uri: string;
        range?: Range;
        context?: string;
    };
}

// Response
interface CodiveExecuteResponse {
    success: boolean;
    result?: string;
    edits?: TextEdit[];
    error?: string;
}

Custom Notifications

// Codive progress updates
interface CodiveProgressNotification {
    id: string;
    stage: "analyzing" | "generating" | "applying";
    message: string;
    percentage?: number;
}

Editor Integration

VS Code

Use the official extension for the best experience.

Neovim

Configure with nvim-lspconfig.

Other Editors

Any LSP-compatible editor can use Codive.

Generic Editor Setup

For editors not explicitly documented, configure your LSP client to:

1. Start codive lsp as the language server
2. Associate it with your desired file types
3. Enable the features you want to use

Example configuration (generic):

{
  "languageserver": {
    "codive": {
      "command": "codive",
      "args": ["lsp"],
      "filetypes": ["rust", "typescript", "python", "go"],
      "rootPatterns": [".git", "Cargo.toml", "package.json"]
    }
  }
}

Troubleshooting

Server Not Starting

Check that Codive is installed and accessible:

which codive
codive --version

Features Not Working

Verify LSP is initialized:

# Check server logs
codive lsp --log-level debug 2>&1 | head -50

High Latency

If responses are slow:

1. Check your API key is valid
2. Consider using a faster model
3. Reduce context by configuring ignore_patterns

[lsp]
# Use a faster model for LSP
model = "claude-3-haiku-20240307"

[context]
# Reduce files included in context
max_files = 20

Connection Issues

For TCP mode, ensure the port is available:

# Check if port is in use
lsof -i :9257

# Use a different port
codive lsp --tcp --port 9258

Next Steps

• Set up the VS Code extension
• Configure Neovim integration