Ktx: An Executable Context Layer to Fix Data Agent Accuracy

Ktx is an open-source executable context layer designed to make AI agents like Claude Code, Codex, Cursor, and OpenCode query your data warehouse accurately. After building production-grade data agents for dozens of companies, the team at Kaelio found that accuracy is the #1 issue: agents generate valid SQL but it's often incorrect due to stale columns, hidden business rules, join fanout, and missing attribution logic.
Ktx splits the problem into two parts:
- Business context goes into Markdown wiki pages that are auto-ingested, organized, deduplicated, and flagged for contradictions.
- Queryable definitions go into YAML files defining tables, row grain, joins, measures, dimensions, filters, and filter groups.
When an agent needs a metric, it asks ktx for a measure, dimensions, and filters instead of writing the whole query. Ktx's planner chooses the join path, uses grain and relationship metadata, catches issues like join fanout and chasm joins, and compiles the warehouse SQL while also leveraging unstructured knowledge from ingested docs.
Ktx integrates with most warehouses (BigQuery, Snowflake, Postgres, ClickHouse, MySQL, SQL Server, SQLite), modeling tools (dbt, MetricFlow, LookML), BI tools (Looker, Metabase), and doc tools like Notion.
Quick Start
npm install -g @kaelio/ktx
ktx setup
ktx status
After setup, ktx status shows readiness checks for LLM, embeddings, databases, context sources, and agent integration.
First Commands
ktx setup # Create, resume, or update a ktx project
ktx status # Check project readiness
ktx ingest # Build context for every configured connection
ktx sl "revenue" # Search semantic sources
ktx wiki "refund policy" # Search local wiki pages
ktx mcp start # Start the MCP server for agent clients
For agent users: run npx skills add Kaelio/ktx --skill ktx in your project directory to install and configure ktx via the skill.
Who It's For
Use ktx if you want agents like Claude Code or Codex to query your warehouse with approved metric definitions, have business knowledge scattered across dbt, Looker, Metabase, and Notion, or need agents to reuse canonical SQL instead of inventing it on every prompt. Skip it if you don't have a SQL warehouse or only need one-off ad-hoc queries.
📖 Read the full source: HN AI Agents
👀 See Also

Claude Desktop App Adds Projects Feature to Cowork Interface
The Claude desktop app now includes a Projects feature in Cowork, allowing users to organize tasks and context in dedicated workspaces. Files and instructions remain on the user's local computer, with options to import existing projects or start new ones.

Claude Code's Illusion of Finished Work: Why Reviewing the Agent's Path Matters More Than the Diff
Claude Code can produce a clean diff, passing tests, and a good summary—yet still miss real behavior, security concerns, or architecture constraints. The author argues that reviewing the chain of actions (plans, files read, commands run, test output) is now essential, not just the final diff.

How Mendral Cut LLM Costs by Upgrading to Opus: Triager Pattern, SQL Access, and Sub-Agent Architecture
Mendral switched from Sonnet to Opus 4.6 for CI failure analysis but reduced costs by using a Haiku triager to divert 80% of failures, giving agents SQL access to ClickHouse instead of pushing logs, and spawning cheap sub-agents to do the actual digging.

Memorine: A Local Memory System for OpenClaw Agents Using Python and SQLite
Memorine is a local memory system for OpenClaw agents that uses only Python and SQLite, with no external dependencies, API calls, or telemetry. It provides fact storage with full-text search, memory decay, contradiction detection, causal event chaining, and optional semantic search via fastembed and sqlite-vec.