Kin Graph
Give your AI a map of your code.
See what calls a function, where a change might reach, and which code to inspect next.
Explore the standalone Graph tools today. We plan to bring this code context into your Kin connection.
publishRelease()runChecks()buildAssets()Understand the reach of a change.
Look beyond
the edited function.
Use Kin Graph to inspect recorded callers and related code before you edit. Follow a connection to the source and check what else needs attention.
Kin Graph keeps source, recorded relationships and history together as versioned repository data. A connection gives you a reason to look closer; it does not guarantee a change is safe.
Keep the context of the change.
Compare changes in context.
Kin Graph versions the source and its recorded relationships. Inspect an earlier state beside the current code when you need to understand how behavior changed.
function publishRelease() {
runChecks();
}function publishRelease() {
runChecks();
+ buildAssets();
}Work with the code you have.
Existing tools.
A shared code record.
The standalone Graph tools support local repository workflows for people and coding agents. Start with the languages and interfaces your workflow needs.
How ordinary files fit
Supported tools can use ordinary files while Kin Graph owns the repository state. Kin Graph's local repository storage and queries run on your machine. Functions, types and recorded relationships are versioned repository data, rather than a disposable search index.
How Kin Graph and Git fit together
Kin Graph has its own version control, with Git import and supported export workflows. Bring edits made outside Kin Graph into its record before relying on it. Kin Graph and Git maintain separate histories.
How people and AI use the same context
People and supported coding agents can query the same Kin Graph repository through its interfaces. An agent runner is optional. Check language coverage and repository readiness before relying on a graph answer.
Explore Graph with code you know.