Repository navigation
v0.6.0-beta.1 — telemetry is now sent
Pre-releaseThis release sends anonymous usage statistics. Earlier versions recorded them to a local file and transmitted nothing. The first run prints a notice saying so, once.
semlayer telemetry --show # exactly what would be sent, before it is
semlayer telemetry --off # off permanently
semlayer telemetry --on # back on
semlayer telemetry # which switch is in effectSent: command, duration, outcome, error class, warehouse type, bucketed table and column counts, per-stage timings, version, Python major.minor, OS, architecture.
Never sent: table or column names, schema or database names, connection URIs, credentials, SQL, cell values, file paths.
That is enforced rather than promised. Every field passes through a whitelist — a caller cannot send an undeclared key, and counts are bucketed in the serializer rather than at call sites, so an exact count cannot escape even by mistake. Full field list and reasoning: docs/telemetry.md.
Events collected by earlier versions are discarded, not sent. They were recorded while the documentation promised nothing left your machine, so transmitting them would make that promise retroactively false. The first run of this version deletes the existing spool and starts fresh.
Sending happens at the end of a command, in a background thread with a 1.5-second deadline. A slow or unreachable endpoint cannot slow or hang your command, and the spool is cleared only when the server confirms receipt — a failure never destroys pending events.
Ordinary mistakes no longer look like crashes
A mistyped filename and an unsupported warehouse URI both produced a Python traceback. They now produce an error and a hint:
$ semlayer validate nope.yaml
FAIL nope.yaml
file not found: nope.yaml
$ semlayer infer snowflake://nope
error: unsupported source uri: snowflake://nope
hint: expected one of: snowflake, bigquery, duckdb:<path>, postgres, postgresql://<dsn>
validate reports a missing file and carries on with the rest, rather than stopping on the first.
The telemetry off switch now works
telemetry.py previously documented a telemetry key in ~/.semlayer/config as a way to disable it. Nothing ever read that file — there is no config file in this package. Only SEMLAYER_TELEMETRY worked, so anyone who followed that instruction had not opted out. Nothing was transmitted either way, because no sender existed; this was fixed before one did.
--no-llm is documented more precisely
SECURITY.md said it meant "nothing leaves your environment at all". It means no schema, column names, or sample values reach a model provider — a statement about where your data goes, not about all network traffic. Corrected before telemetry made the old phrasing false, not after.
Install: pip install semlayer==0.6.0b1