The file-first model is ending. Kin is the semantic system of record for AI-native software work.Learn more →
Back to Labs

Kin Editor

ActiveApache-2.0

Lightweight VS Code surface for the semantic substrate

Kin Editor is the current VS Code story for Kin. It replaces the older fork-shaped thinking with a focused extension: entity explorer, semantic search, trace, review, rename, and graph-backed navigation on top of the same Kin runtime.

Extension model

MCP first

Persistent graph access when available, CLI fallback when needed.

Scope

Focused UX

VS Code integration without turning the editor itself into the product boundary.

Narrative role

Editor surface

Pairs with kin-vfs and Kin itself instead of reviving a custom editor fork.

What It Adds

Kin Editor is deliberately narrow: it makes Kin legible inside VS Code without moving the system of record into the editor.

Entity explorer

Browse functions, classes, modules, and graph entities in a focused VS Code sidebar.

Semantic search + trace

Search entities by meaning, then trace dependencies and related entities directly through the Kin graph.

Review and rename

Run graph-aware review workflows and semantic rename flows instead of relying only on text-based editor primitives.

MCP-first architecture

The extension prefers a persistent MCP connection to Kin and falls back to CLI subprocesses when needed.

How It Fits

Core runtime

Kin owns the graph, the CLI, and the MCP server. The extension does not replace that core.

Editor UX

Kin Editor turns semantic search, trace, overview, and review into native-feeling VS Code commands.

Projection layer

kin-vfs handles transparent file projection so the editor surface can stay lightweight and focused.