Skip to main content

Reference

Where you can use Kin.

Check your computer and the tools you want to use before installing. Running Kin and making its code available as ordinary files have different platform requirements.

How this works in Kin

Two things vary by platform and they vary separately: whether the runtime is covered, and whether the filesystem projection is. A platform can be a good place to run Kin and a bad place to project files from.

Current release

v0.7.19. Run kin doctor after installing: it names your platform, whether the daemon is reachable, and whether the projection shim is installed and engaged, which is the row most likely to need attention on a fresh machine. That command was last run here on Kin v0.7.6 on 2026-09-09. Current release: v0.7.19.

The matrix

  • macOS, Apple Silicon and Intel

    Runtime

    The graph, vector, daemon, setup, MCP and review surfaces all ship in the release archive.

    Projection

    Shipped and exercised on both architectures. It uses DYLD_INSERT_LIBRARIES, so SIP-protected or hardened programs may reject the injection.

  • Linux x86_64 and arm64

    Runtime

    kin and kin-daemon are static musl builds, intended to run on glibc and musl distributions alike.

    Projection

    The public projection executable and shim are GNU/glibc builds, not musl. They are pinned to a glibc floor of 2.31 and link OpenSSL 3, so a projection host needs both. Debian 12 loads them. Alpine and other musl distributions are not supported projection hosts. The arm64 release proof runs on Ubuntu 24.04.

  • Native Windows x86_64

    Runtime

    Early. Repositories admit, and graph and lexical queries answer natively. MCP and review workflows are not yet covered end to end by the install proof.

    Projection

    Not shipped. WSL2 with a Linux distribution that meets the glibc boundary is the documented path.

Where you can install it from

  • GitHub Releases

    Six archives across five platforms, each with a SHA-256 sidecar, plus a checksums file.

  • npm

    @kinlab/kin and @kinlab/kin-mcp. The wrapper needs Node 20 or newer.

  • Homebrew

    The kinlab/kin tap.

  • MCP Registry

    Published as ai.kinlab/kin.

  • GHCR

    A container image published beside the archives.

The install page carries the exact command per platform, including the separate PowerShell path for Windows.

What has not been measured

Kept here rather than left out, because an unmeasured surface reads exactly like a working one until you depend on it.

  • Version control on native Windows. Not measured.
  • Collaboration across machines. Clone, push and pull work, but the run that showed them had both repositories on one machine. Nothing measured a second machine or a team.
  • Agent clients outside the six named integrations. The release proof exercised one client leg, not all of them.
  • The filesystem projection under any of the release runs. It ships in the public Linux and macOS archives and no run used it. The macOS install proof read the shim as installed and the driver as running, which is a readiness row rather than a use of it.

Next action

Install the build for your platform.

One correct path per platform, with the checksum step, then the quickstart takes you to an answer you can check.

Install Kin

Related