Repository navigation
v0.7.0-beta.1 — the whole loop runs in the chat
Pre-releaseThis release finishes the job you can do from a chat. Add the MCP server to Claude Code, Claude Desktop or Cursor and the whole loop happens there: connect to a warehouse, build the semantic layer, get the context for a question, run the SQL, see what the answer assumed, correct it, and save or export the result. No terminal step, and with uv installed, nothing to install first:
{ "mcpServers": { "semlayer": {
"command": "uvx",
"args": ["--with", "semlayer[warehouses]", "semlayer", "mcp"] } } }You do not need a model key to get a layer
Statistics, primary and foreign keys, join paths, metrics, routing knowledge and the lint all run with no ANTHROPIC_API_KEY. What you lose is the written descriptions, and the layer now says so plainly instead of leaving you to infer it from a model: none string. A layer somebody hand-wrote reports nothing rather than claiming to be ours.
Every answer carries what it assumed
run_sql runs one read-only SELECT and returns the rows with assumptions underneath: the claims nobody has confirmed, what the engine saw, and whether accepting one would change behaviour. Say yes and review_answer records it, signed, and writes it through to the layer file — the claim stops appearing on the next answer, and the verdict outlives the session.
Who may decide what is a line, not a setting. An agent may accept a claim where accepting changes no behaviour. It may not accept one that unlocks behaviour — a decode guess, an aggregate table becoming routable, a discovered filter, two columns being the same thing. There it proposes with its reasoning and a person confirms.
SELECT-only, decided by parsing
DELETE, UPDATE, INSERT, MERGE, CREATE, DROP, TRUNCATE, GRANT, COPY, SELECT … INTO and a second statement after a semicolon are refused. A column named deleted_at is not a write, and a parse knows that where a word search does not. Your SQL is never rewritten — no LIMIT appended, no filter injected: a required filter is reported and left undone, so what ran is what you can be shown. Ten-minute default time limit, enforced by the warehouse itself.
infer shows a progress bar, and the server answers while it runs
The four loops that take the time report from inside themselves, so you get "profiling table 24 of 36", a monotonic percentage and a rough ETA, streamed to your client as MCP progress. The stage weights behind that percentage were measured on a live 116-table run, not assumed.
A synchronous infer used to freeze the whole server for the length of its wait — a status sent one second in went unanswered for 5.9 more. It is now answered in hundredths of a second, with a regression test that fails against the old version.
A credential pasted into the chat works, for that session only
The agent is still told never to ask for one. When it happens anyway, the value is held in memory and goes nowhere else: not to disk, not to a log, not into telemetry, the layer, the run report or the cache key. status shows the connection redacted, and the redacted form is what the cache is keyed on.
The benchmark table was not re-measured for this release
docs/benchmark.md still describes 0.6.0b1, and this release does not restate it. Read every row as 0.6.0b1. The engine has since changed in a way that reaches the benchmark's prompts, so some committed recordings no longer replay; the release workflow runs that check and prints its result, and at this release it does not block publishing. Re-recording and re-measuring is owed before any number on that page can carry 0.7.0b1. Both causes are written down at the check itself.
Telemetry: the new MCP tools and the setup prompt join the tools whitelist, and an inference started by an agent is recorded with via: mcp. No new fields. What is sent and what is never sent: docs/telemetry.md.
Full detail in CHANGELOG.md.