Open-source Kin: public developer alpha

Install Kin. Ask the graph.

The installer provisions the verified Kin CLI and daemon, then Kin's own setup and status commands tell you exactly what is ready.

v0.3.4e75570c9ac84Channel: AlphaCurrent public release

Canonical installer · macOS / Linux

curl -fsSL https://get.kinlab.dev/install | sh
Release metadata is pinned above. Inspect the installer or build from source before running it if that is your security policy.

First useful result

The shortest useful path

Run setup once, initialize a repository, verify live status, then get an answer from graph + lexical signals. Add vectors only if you need them.

  1. 01kin setupConfigure Kin and any supported detected agent clients.
  2. 02cd /path/to/repositoryEnter the repository you want Kin to understand.
  3. 03kin initInitialize graph-owned semantic truth for this repository.
  4. 04kin statusConfirm that the repository graph is ready.
  5. 05kin setup status --jsonVerify the machine and MCP configuration from Kin itself.
  6. 06kin locate "where are webhook retries handled"Get the first answer from graph + lexical signals; vectors are not required.
  7. 07kin embedOptional: add vector similarity. The default model download is roughly 522 MB; budget about 2 GB of available memory for public-alpha use.

Kin setup reports what it actually configured. It is not a promise that every client on every machine was wired automatically.

Core is broader than projection

Check the VFS boundary before you install

The Kin core and Kin VFS have different platform envelopes. VFS is an optional graph-derived filesystem projection, not a requirement for CLI, daemon, or MCP use.

macOS

Core
Supported
VFS
Limited by host security

The Kin core supports Apple Silicon and Intel. VFS projection uses DYLD injection and may be blocked by SIP or hardened executables.

Linux

Core
Supported
VFS
Compatible glibc only

The core supports x86_64 and aarch64. Released VFS projection requires a compatible glibc host; Alpine/musl and some Debian 12-class hosts may run the core without projection.

Windows

Core
Supported, vector-free
VFS
Unavailable natively

The native Windows build is a supported vector-free runtime for graph, lexical, daemon, setup, and MCP workflows. Vector similarity and filesystem projection require WSL2.

Alternate install paths

Use these when the canonical shell installer does not match your environment. They install the same public Kin release surface.

npm package

npm i -g @kinlab/kin
kin setup

Native Windows PowerShell

irm https://get.kinlab.dev/install.ps1 | iex
Review the build-from-source steps

One graph, three local surfaces

Start with open-source Kin. Hosted KinLab onboarding is separate, proprietary, and currently available by request.

CLI and daemon

Initialize a repository, maintain its semantic graph, and query it from the terminal.

Kin Editor

Add entity exploration, semantic search, trace, and review providers to VS Code.

Bundled Kin MCP

Expose graph-backed locate, context, and trace tools to supported AI-agent clients.