Documentation/

Editor Setup

AI-powered editors like Cursor, Windsurf, and Zed need JSON config files to connect to your project tools. You'd write them by hand, get the paths wrong, and repeat it for every project.

One command configures your editor. The AI assistant inside it gets build, test, lint, search, and file operations — no manual JSON editing.

Configure an Editor

8v editor setup cursor        # Writes .cursor/mcp.json
8v editor setup windsurf      # Writes .windsurf/mcp.json
8v editor setup zed           # Writes/merges .zed/settings.json

Each command writes the configuration file your editor expects, in the right location, with the right format. If a config file already exists, 8Vast merges its settings without overwriting yours.

Configure All Editors

8v editor setup all           # Configures all detected editors

This checks which editors are installed and writes config files for each one.

Check Status

8v editor status              # Shows which editors are configured

This lists each supported editor, whether it's installed, and whether the config file is present and valid.

What Your Editor Gets

After setup, your editor's AI assistant can:

  • Build and test your project
  • Lint and format code
  • Search your codebase by keyword or meaning
  • Read and write files
  • Run git operations

These capabilities appear as tools inside your editor's AI panel. You don't invoke them manually — the AI assistant uses them when relevant to your conversation.

Per-Project

Editor config files are written to the current project directory (.cursor/mcp.json, .windsurf/mcp.json, .zed/settings.json). Run 8v editor setup in each project where you want the integration.

Next

  • AI Agents — launch CLI-based agents with project tools
  • Custom Tools — define your own tools that editors can use

Referenced by