**This PR is the 0.7.19 release** (`scripts/release/bump-version.sh
patch`): merging it runs Publish Release. Its receiver changes under
`apps/api` deploy on the same merge through Deploy API, minutes before
PyPI has 0.7.19, so schema 4 is read before any client sends it.
Fixes for what PostHog's first day of telemetry showed (2026-10-08
00:14Z to about 21:40Z: about 209 installs and 59 crash reports). It
covers three bugs people are hitting, crash reports that were not
cadgen's bugs, and gaps in what the receiver lets us see. There is one
commit per fix.
## Bugs
**1. Builds that export a mesh crashed on Windows** (7 installs, all
Windows, about 26 crashes). `mesh_export.py` ran the Node exporter with
`text=True` and no encoding, so Windows read its UTF-8 output in the
local code page. The exporter's JSON report names every output path, so
any output folder whose name the code page cannot read (for example
`Рабочий стол` under cp1252, or most Chinese text under cp936) made
CPython's Windows output reader die quietly. `proc.stdout` came back
`None`, and `.splitlines()` raised an `AttributeError`. The exporter now
reads `utf-8` with `errors="replace"`, which keeps the JSON line intact.
The same fix goes into `run_node_builder`, whose input was also silently
empty under cp1252. ffmpeg, `gz sdf` and `doctor` now read `utf-8` with
`errors="backslashreplace"`, and doctor's child process is set to
`PYTHONIOENCODING=utf-8`. The tests force subprocess's default encoding
to cp1252, and both fail without the fix.
**2. `cad_file` failed on 48 of 49 calls on Windows** (5 of 6 installs).
Codex for Windows names a file opened from its file tree as
`openai/resource.path = "/C:/Users/…"`, read from the desktop bundle.
Python 3.13's `ntpath.isabs("/C:/…")` is False, so every call answered
"not an absolute path". The `file.resourceUri` alongside it is a
`codex-resource://` handle, so the fallback never helped. A new
`local_path` drops the slash before a drive on Windows, both for file
URIs and for plain paths, for `cad_file`, `cad_open` and `cad_show`.
This most likely also explains Antigravity's `cad_show` failures on
Windows (7 of 12). The Windows CI job now passes the path the way Codex
spells it.
**3. `cad_screenshot` failed on 30% of calls** (11 of 19 installs). The
most likely cause is an agent capturing straight after build, show or
open, while the view is still loading or has not synced yet. The view
refused with "Wait for the displayed model revision to finish loading",
"That viewer is not open" or "No CAD viewer with a model is open", or a
large model ran past the fixed 10 s wait.
- The page now waits until the view shows the requested model, loaded
and drawn (`CAPTURE_SETTLE_MS`, 20 s).
- The server waits for a view it just opened to sync (`OPENING_SECONDS`,
15 s) within one budget for the whole capture (`CAPTURE_SECONDS`, 40 s).
- The capture's reply still goes on its own call (`void answer(event)`),
so no view call is held open.
## Crash reports that were not cadgen's bugs
- **Windows viewer disconnects.** `ConnectionAbortedError` (WinError
10053) made up most of the crash volume: 23 installs. The viewer caught
only `BrokenPipeError` and `ConnectionResetError`, and the header write
had no guard. Every write to the socket now treats any `ConnectionError`
as the page having left.
- **A model's own mistakes.** A build123d name that does not exist,
raised through the `cadgen.build123d` re-export, and a non-string passed
to `srgb()`. Both now raise deliberately, so the existing rule counts
them as the person's error, and `srgb` raises a `TypeError` naming what
it was given.
- **Stopped workers.** A worker stopped by SIGTERM, SIGINT or SIGHUP (a
person quitting it, a logout) now counts as cancelled, not crashed.
SIGSEGV, SIGABRT and SIGKILL are still reported.
## Telemetry: what we can now see
- **Why a tool call failed.** There is a new `tool_failure {tool,
reason, count}` event in batch schema 4, which PostHog receives as
`tool_failed`. The reason is one word from a fixed list (`no_path`,
`relative_path`, `no_file`, `not_cad`, `no_view`, `wrong_view`,
`bad_request`, `timeout`, `view_error`, `too_large`, `no_viewer`, `bug`,
`other`), chosen where the call fails and never taken from a message. A
test checks that every `ToolFailed` and `NoAnswer` names one.
- **Rollout: the receiver goes first.** The API is its own Vercel
project now (#587) and deploys on merge to `main`, so merging this PR
puts the schema 4 receiver live before any release sends schema 4. A
refused batch is dropped, as before; there is no fallback in the client.
- **Refused batches are logged.** Each 400, 403 or 415 is one
`console.warn` line naming the rule that failed and the cadgen version.
Values, install ids and service messages are never logged. Vercel's
per-status counts need Observability Plus, so this is the only way to
see a refusal. The privacy policy says so.
- **Errors are logged by name**, for example `TimeoutError` instead of
`23`. A `/v1/forget` timed out at 17:02Z, and the client retries it.
- **`$session_id`** is now set, so error tracking can count sessions.
Our ids are UUIDv4, so PostHog's sessions table leaves them out; error
tracking should still read them, which needs checking after deploy.
Privacy policy, README and `apps/api/README.md` are updated where what
is sent or logged changed.
## Not in this PR
- **Deduplicating a resent batch.** The sender rebuilds a failed window
instead of resending it, and a batch has no id, so there is nothing
stable to dedupe on yet. It needs a per-batch id from the sender.
- **Dashboard totals.** PostHog's error-tracking "occurrences" counts
events, not each event's `count`; for the mesh-export crash that is 5
against 22. That is fixed on the dashboard side (t2c-analytics).
- **5 of 15 DXF builds failed.** DXF builds don't go through Node, so
the encoding fix doesn't cover them and they still need a look.
## Needs a real host
- Windows Codex: open a `.step` from the file tree; capture from a tab
hidden behind another tab.
- Claude Desktop: capture right after `cad_show` on a large STEP, or
while the card waits on Allow.
- Antigravity on Windows: confirm the path spelling it sends.
## Tests
Full suites on this branch, in a provisioned worktree (`.venv` from
`requirements-dev.txt`, `npm ci`, `bundle.sh --check`,
`CADGEN_DAEMON=0`): all pass.
- `scripts/test/test-python.sh --keep-going`: 2,774 tests in 8 groups,
OK.
- `scripts/test/test-js.sh`: every group passes (core, ui, web, mcp).
- `scripts/test/test-docs.sh`: receiver tests 30/30 and the rest 16/16.
- `scripts/test/test-global.sh`: 210 tests, OK (1 skipped).
Each new regression test was run against the old code, and each fails
there.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Releases 0.7.18: VERSION, the derived metadata and every cadgen pin.
Opened by Prepare Release. Merging it releases it: Publish Release
uploads the wheel to PyPI, then moves the latest branch.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Release 0.7.17: no telemetry is lost when a CAD app, viewer or daemon
exits, and no exit waits on the network.
## The bug (0.7.16)
A CAD Viewer asked to exit (`cadgen viewer stop`, a newer launch,
SIGINT/SIGTERM) hard-exits 0.5 s later (`viewer/main.py`), but its last
send only began once `serve_forever` had returned. Against production,
the exit always won: the viewer sends every 5 minutes, so everything
since its last batch was lost, crash reports included, and a viewer that
ran under five minutes sent nothing at all. Found by the post-release
check of 0.7.16 against `api.texttocad.dev`: the CAD app's batch
arrived, the viewer's never did; with the viewer kept alive past its
5-minute send, its batch (view, files, Quick Edit, a page crash) arrived
and was taken.
## The fix
No exit sends any more (law 19: nothing waits on the network).
- `Recorder.close` keeps the process's last batch, whole, in
`telemetry-batches.jsonl` beside the settings: a local write, only while
sharing is on, under the answer in force, capped like the spool (256
KiB). A file of its own, so a 0.7.16 still installed never reads it.
- The next process that sends sends it in the background, `KEPT_SECONDS`
(10 s) after it starts, and with every flush (`send_kept`), each batch
as it was made. Only under the same answer: a no deletes the file, and a
batch kept under an earlier answer is dropped. A batch the receiver did
not take is kept again.
- The viewer starts keeping its batch as soon as it is asked to exit;
the hard exit frees the port at 0.5 s as before and waits at most 1 s
for that local write.
- The two-second exit wait (`CLOSE_SECONDS`) is gone from `cadgen mcp`,
the viewer and the build daemon. Law 19 (`packages/cadgen/README.md`),
the README's Telemetry section and the privacy policy say so; the one
wait left is `cadgen telemetry off`, which waits for the deletion it
asks for.
Trade-off: a batch kept at exit arrives when the next cadgen process
starts, so its events are stamped then rather than when the process
exited.
## Tests
- `test_a_stopped_viewer_keeps_its_last_batch_for_the_next_process`
(real viewer process, a receiver that hangs): the viewer exits promptly,
sends nothing, and the kept file holds its batch.
-
`test_an_exiting_process_waits_on_nothing_and_the_next_one_sends_its_last_batch`:
close returns in well under a second with the network hanging; the next
recorder sends the batch as made (its process, session, client), keeps
it again when offline, and never twice.
- `test_a_kept_batch_is_sent_only_under_the_answer_it_was_kept_under`: a
no deletes it; nothing is kept under a no; a process with
`CADGEN_TELEMETRY=0` leaves it; another answer since drops it.
-
`test_a_started_recorder_sends_what_was_kept_a_moment_after_it_starts`.
- The daemon's last batch is kept and sent by the next process.
- Local: global 210, viewer 369, MCP 81,
daemon/telemetry/crash/doctor/updates 64 — all pass.
## Release
`VERSION` 0.7.16 → 0.7.17 (`scripts/release/bump-version.sh patch`);
merging releases it.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Releases 0.7.16: VERSION, the derived metadata and every cadgen pin.
Opened by Prepare Release. Merging it releases it: Publish Release
uploads the wheel to PyPI, then moves the latest branch.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Releases 0.7.15: VERSION, the derived metadata and every cadgen pin.
Opened by Prepare Release. Merging it releases it: Publish Release
uploads the wheel to PyPI, then moves the latest branch.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.14. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.13. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.12. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.11. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.10. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.9. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.8. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.7. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.6. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.5. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.4. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.3. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.2. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.1. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.7.0. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.6.6. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.6.5. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.6.4. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.6.3. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bumps VERSION, derived package/plugin metadata and every skill's cadgen pin to 0.6.2. Prepared with the same steps as Prepare Release; the merge into main runs Publish Release.
Since 0.6.1: #396 (dependabot bumps), #401 (viewer vite 8 and React 19), #406 (Smart App Control hint, fixes#404), #408 (test fixtures built once per class).
Bumps VERSION, derived package/plugin metadata and every skill's cadgen
pin to 0.6.1. Created by Prepare Release, which merges it into main
immediately; the merge runs Publish Release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
