Kith for VS Code and CursorOne extension connects your editor's agent to Kith and adds a small read-only status indicator. Kith's coordination server is bundled; no global npm install is required. InstallUse Extensions → Install from VSIX and select The extension offers Kith through the editor's native MCP API. The editor still controls server approval, tool permissions and start/stop. Existing Kith server entries are preserved and suppress a duplicate registration. Other MCP servers, hooks and permissions are untouched. VS Code 1.102+ and a Cursor version exposing its MCP extension API are required. Tell the agent which repository contains the task. The same connection supports multiple repositories through Kith's Click Kith in the status bar or run Kith: Show Workspace Status. It observes linked-worktree dirty paths and reads existing coordination state offline. It does not initialize a project database, attribute writes to processes, enforce non-cooperating editors, or certify that changes merge. An unavailable scan stays unavailable. No telemetry or model calls are added. DevelopmentFrom the repository root, install core dependencies with
The VSIX is written to Native API references: VS Code MCP provider, Cursor MCP registration. Native host checks on macOS passed with VS Code 1.143.0 and Cursor 3.24.18 (VS Code API 1.128.0): extension activation, native MCP registration, refresh, and no workspace configuration or database creation. These checks do not sign in, approve tools, or make model calls. Separate real MCP workflow tests exercise the bundled server through verified integration in two disposable repositories, including refusal of a capability from the other repository. CI checks the minimum VS Code version too. |
