Skip to main content

A new foundation for code.

A code repository that versions the connections, not just the code.

Built for AI and the people who use it.

Try Kin See how it works
npx -y @kinlab/kin setupOther ways to install

Works on macOS, Linux, Windows and WSL. Needs Node.js 20 or newer.

Open source. Public alpha.

More code is only part of the work.

AI can write the change. You still need to understand what it touches, decide what to check, and carry that knowledge into the next task.

The work around the change

  • Work out what it touches.

    Read the code until you know what the change reaches.

  • Decide what to check.

    Pick the places that need a second look before it ships.

  • Keep what you learned.

    Nothing in the repository holds that answer, so the next change starts the same loop.

What else uses this?

Follow a recorded connection from a function to the code that calls it. Check the answer against the source.

Input updates
Text area updates
Shared function
Selected connections from a recorded React snapshot. Coverage is partial.
Inspect the saved example

The connections belong with the code.

Kin makes recorded relationships part of the repository's own version history. They are part of the record you work from, not a separate explanation of it.

Explore the architecture
Repository model illustrated
NAMED CODE BILLINGInvoice calculationtotal_with_tax()billing.py
COMMERCECheckoutcheckout()
DOCUMENTSReceiptmake_receipt()

One calculation used in two places.
The repository remembers both; the arrows show which code uses which.

Repository model illustrated

01 / THE WAY IN

Start with your code.

  • A new native Kin project
  • An existing Git repository

Import and language tooling build the record from supported code.

02 / THE REPOSITORY

A connected record.

  • Named code
  • How pieces connect
  • Recorded changes

A change is recorded against the actual code it affected, not a range of lines, always with an author and a message. Kin won't record a change with no author at all.

03 / THE WAY YOU WORK

Familiar files.

  • Files for your editor and builds
  • Answers for you and your AI tools

Your files stay on disk. Your editor, compiler and other tools keep opening them exactly like before.

Language coverage varies, and not every connection gets caught. The record helps you find where to look. You still decide on the change and check that it works.

Direct the work. Inspect the change.

Use the same recorded connections to guide an agent and inspect the code it changes. Keep your review grounded in the source, not just the agent's explanation.

PeopleAgents
One repository record
CodeHistory
People and agents work from the same repository record.

  1. Direct

    Give the agent a task and an inspectable starting point.

  2. Inspect

    Follow recorded connections back to the source.

  3. Decide

    Choose what needs checking before recording the change.

Workflow illustration, not an approval interface. Supported local workflows. Tests and human review still matter.

Connect your AI tool

Give the next change a better starting point.

Inspect the recorded connections. Make a change. Record it in Kin. Return to that state when the next task begins.

CodeConnectionsHistory

Bring edits made outside Kin into its record before relying on it. Kin and Git maintain separate histories.

Understand the recorded history

What Kin has shown so far.

Every result on this page comes from a saved run you can check. Here is where each one stops.

Shown, with the output

  • Source, code entities, relationships and version history are stored as repository state.
  • A saved React answer: eight recorded callers of getToStringValue on one revision, checked against the source.
  • A saved session on Kin 0.7.19: the same callers before and after a recorded change, from the terminal and over MCP.

Not claimed

  • Complete coverage. Kin can miss connections, and an empty answer does not prove nothing is connected.
  • Faster reviews, lower cost or fewer bugs. Those need measurements we have not published.
  • Safe changes. Tests and review still decide whether a change is right.
  • Hosted team collaboration. KinLab, our product for teams, is in development.
See the evidence and how it was gathered

Try Kin on your own code.

Kin is in public alpha. Start with a disposable copy of a small, supported project.

Try Kin
npx -y @kinlab/kin setup

Requires Node.js 20 or newer. Downloads need network access.

Other ways to install