explaingit

kaelio/ktx

Analysis updated 2026-07-03 · repo last pushed 2026-07-03

⭐ Rising1,450TypeScriptAudience · dataComplexity · 3/5ActiveSetup · moderate

TLDR

ktx lets AI coding assistants query your data warehouse correctly by scanning your dbt, Looker, and docs to build a local knowledge base of approved metrics, table relationships, and business rules.

Mindmap

mindmap
  root((ktx))
    What it does
      Builds knowledge base
      Generates read-only SQL
      Flags contradictions
    Data sources
      dbt models
      Looker dashboards
      Notion and wikis
    Key features
      Runs entirely locally
      Read-only by design
      Consolidates context
    Tech stack
      TypeScript
    Use cases
      Reliable agent data queries
      Consistent company metrics
    Audience
      Data teams
      Analytics engineers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let an AI agent answer data questions using your company's approved metric definitions instead of guessing.

USE CASE 2

Consolidate scattered analytics knowledge from dbt, Looker, and Notion into one searchable source for agents.

USE CASE 3

Automatically generate read-only SQL queries with correct table joins pulled from your existing analytics tools.

USE CASE 4

Detect and flag contradictions in metric definitions across different tools so your team can review them.

What is it built with?

TypeScriptdbtLookerMetabaseSQL

How does it compare?

kaelio/ktxyorgai/org2shy3130/tickflow-stock-panel
Stars1,4501,4281,368
LanguageTypeScriptTypeScriptTypeScript
Last pushed2026-07-032026-07-032026-07-03
MaintenanceActiveActiveActive
Setup difficultymoderatemoderatemoderate
Complexity3/53/53/5
Audiencedatadeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires connecting at least one analytics source (dbt, Looker, or Metabase) plus an LLM provider API key.

No license information was provided in the explanation, so the specific permissions for using this code are unknown.

In plain English

ktx is a tool that helps AI coding assistants like Claude Code, Codex, or Cursor query your company's data warehouse accurately. The core problem it solves is simple: when you ask an AI agent to pull data or answer an analytics question, it usually doesn't know your business logic. It might guess how tables connect, invent its own definition of "revenue," or return numbers that don't match what your finance team actually uses. ktx bridges that gap by giving the agent a ready-made understanding of your metrics, table relationships, and business rules before it ever writes a line of SQL. At a high level, it works by scanning your database, your existing analytics tools (like dbt, Looker, or Metabase), and even your team wikis or Notion docs. It pulls all of that together into a local knowledge base, part structured definitions, part searchable wiki. When an agent then needs to answer a question, it goes through ktx rather than guessing. ktx hands it the approved metric definitions, figures out the right table joins, and generates read-only SQL that runs against your warehouse. It also flags contradictions it finds across your sources, so a human can review them. This is aimed at data teams and analytics engineers who want to let AI agents handle data tasks without babysitting every query. If your company's knowledge about metrics is scattered across dbt models, Looker dashboards, and random Notion pages, ktx consolidates that into one place agents can actually use. It's not for one-off queries, it's for teams who want agents to repeatedly and reliably answer questions using the same definitions everyone else in the company uses. A few things stand out. It runs entirely locally, so your schema and query results don't go to any hosted service, only whatever you send to your chosen LLM provider. It's read-only by design, meaning it can't accidentally modify your database. And it doesn't replace tools like dbt's semantic layer, it ingests them and adds context on top, giving agents a single surface to search rather than juggling three disconnected ones.

Copy-paste prompts

Prompt 1
Help me set up ktx to scan my dbt project and Looker instance so my AI coding assistant can query our warehouse with approved metric definitions.
Prompt 2
Using ktx, how do I connect my Notion workspace and Metabase so the agent has full context on our business logic before writing SQL?
Prompt 3
Walk me through configuring ktx locally so that schema and query results never leave my machine while still sending prompts to my LLM provider.
Prompt 4
How do I use ktx to flag contradictions between metrics defined in dbt and metrics defined in Looker so I can review and fix them?

Frequently asked questions

What is ktx?

ktx lets AI coding assistants query your data warehouse correctly by scanning your dbt, Looker, and docs to build a local knowledge base of approved metrics, table relationships, and business rules.

What language is ktx written in?

Mainly TypeScript. The stack also includes TypeScript, dbt, Looker.

Is ktx actively maintained?

Active — commit in last 30 days (last push 2026-07-03).

What license does ktx use?

No license information was provided in the explanation, so the specific permissions for using this code are unknown.

How hard is ktx to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ktx for?

Mainly data.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub kaelio on gitmyhub

Verify against the repo before relying on details.