The file-first model is ending. Kin is the first layer of what comes next. Learn more →
Back to Labs

Kin Code

Open Source Coming Soon TypeScript MIT

Kin-Native Editor

What if your editor understood code the way you do — not as files, but as meaning? Kin Code is a Code - OSS fork where the semantic graph is the primary workspace. Files still exist as projected working surfaces, but the graph is what you navigate, search, and review.

Coming Soon Back to Labs

The Problem

Today's Editors

  • Open files by path
  • Search by filename and grep
  • Navigate directory trees
  • Review line-level diffs
  • Context = whatever files are open

Kin Code

  • Open entities by meaning
  • Search by function, type, relationship
  • Navigate the semantic graph
  • Review entity-level impact
  • Context = precise graph traversal

What Kin Code Adds

Semantic Workspace

Open a Kin repository as a virtual workspace. The graph is the primary navigation surface, not the file tree. Browse entities, relationships, and impact chains directly.

Graph Search

Find entities by what they do, not where they live. Search functions, types, and relationships across the entire codebase without knowing file paths.

Semantic Review

Review changes at the entity level with impact visualization. See what a change actually affects downstream — not just which lines moved.

Provenance Built In

Every entity carries its history — who changed it, when, why, and what evidence supports the change. Audit trails are native, not bolted on.

Files When You Need Them

Files are still there as projected working surfaces. Open, edit, save — it all works. The graph is primary, but the familiar file experience is preserved.

How Kin Code Fits

Kin Code sits between Kin (the VCS) and KinLab (the hosted platform). It's the local development surface where individual developers interact with the semantic graph daily.

Kin Code is coming soon. Sign up to get notified when it launches.