Editor Integrations

Sight's language server supports any editor with an LSP client. This page covers generic LSP setup and AI agent configurations.

For editor-specific guides:

• VS Code / forks: Install from the VS Code Marketplace, from the OpenVSX Registry, or from the GitHub releases page
• Neovim: See Neovim Setup
• Zed: See jbearak/zed-stata

Generic LSP Client

Any LSP client that supports stdio transport can use the Sight server:

sight --stdio

Configure your editor's LSP client to run this command for .do, .ado, and .mata files.

See Standalone Installation for installation options.

Agent Integration

Each tool below requires sight to be installed globally and available on your PATH. The VS Code extension bundles its own copy of the server that is only accessible to VS Code — it does not make the binary available to other tools. Install it separately from source or a release binary:

# From a Sight checkout
./scripts/setup.sh

See Standalone Installation for additional install options.

Claude Code

Install the sight-lsp plugin from the jbearak/claude-plugins marketplace:

/plugin marketplace add jbearak/claude-plugins
/plugin install sight-lsp@jbearak

The plugin configures Claude Code to launch Sight for Stata files (.do, .ado, .doh, .mata).

Kiro CLI

Create lsp.json in your project root:

{
  "languages": {
    "stata": {
      "name": "sight",
      "command": "sight",
      "args": ["--stdio"],
      "file_extensions": ["do", "ado", "doh", "mata"],
      "project_patterns": ["sight.toml"]
    }
  }
}

OpenCode

Create an opencode.json file in your project root:

{
  "$schema": "https://opencode.ai/config.json",
  "lsp": {
    "stata": {
      "command": ["sight", "--stdio"],
      "extensions": [".do", ".ado", ".doh", ".mata"]
    }
  }
}

Crush

Create a crush.json file in your project root:

{
  "$schema": "https://charm.land/crush.json",
  "lsp": {
    "stata": {
      "command": "sight",
      "args": ["--stdio"],
      "extensions": [".do", ".ado", ".doh", ".mata"]
    }
  }
}

Troubleshooting

• Server not found: Ensure sight is on your PATH. See Standalone Installation for install options.
• No diagnostics: Check that files have a .do, .ado, .doh, or .mata extension.
• Logs: Run with SIGHT_TEST_LOG=1 environment variable for verbose output.