Neovim / Vim / Emacs Integration Guide

Overview

Many developers prefer terminal-based editors like Neovim, Vim, or Emacs. Cup’n’String governs these editors and their AI assistants (like Copilot.vim or custom LSP servers) using the compatibility adapter and network isolation.

Support level

Compatibility Adapter + Process & Network Governance

What Cup’n’String detects

• Neovim, Vim, and Emacs process signatures
• Active LSP (Language Server Protocol) server connections
• Outbound API sockets opened by editor plugins

What it governs

• Outbound network requests from terminal-based plugins
• Shielding of sensitive .env files and workspace directories
• Redaction of API credentials in the environment

Recommended policies

• Redirect all editor LSP and AI assistant traffic through the local proxy
• Shield SSH keys and cloud configuration folders from terminal editor sub-processes
• Require administrative approval for raw terminal execution tools

Setup outline

1. Ensure the Cup’n’String agent is active.
2. Run your editor (e.g. nvim).
3. The compatibility adapter intercepts plugin network calls and applies baseline rules.

Verification

Configure a Copilot extension in Neovim and verify that its requests route through the local proxy with token usage tracked.

Troubleshooting

If plugin requests bypass the proxy, check that system proxy environment variables (HTTP_PROXY, HTTPS_PROXY) are correctly inherited by the terminal shell.

Known limitations

LSP inspection depth is limited compared to native IDE integrations like VS Code.