Part 13 of 16
SDKs
Which SDK to install and why, both in-repo clients in full, and a dated list of what is broken in the other estate.
- Which SDK should I use?Two SDK estates publish into the same @cuecrux/ npm scope. This page names the canonical one, gives the install commands, and states the version each registry actually serves as of 2026-07-27.
- TypeScript SDKComplete reference for @cuecrux/client: the seventeen methods of CoreCruxClient, all thirty-three exported types, the CoreCruxError model, and the four runtime behaviours that are not visible in the t
- Python SDKComplete reference for corecrux-client: the sixteen methods on both the sync and async clients, all eight dataclasses, the CoreCruxError model, and the build-twice-and-diff reproducibility gate on its
- AuthenticationHow an SDK consumer authenticates against the Crux Daemon and the hosted CueCrux Engine: where the token goes, which environment variables exist and who reads them, the scope each method needs, and wh
- Errors and retriesThe error classes each SDK throws, what every status code means for recoverability, which calls are safe to retry, which will silently duplicate your data if you do, and how to write the retry loop no
- SDKCrux packagesThe complete SDKCrux inventory: twenty-one packages across three publishing regimes, with the version and real registry status of each, plus full API reference for @cuecrux/memory, @cuecrux/engine-cli
- Known issuesA dated, standing disclosure of every blocking defect, stale artefact and documentation contradiction found in the CueCrux SDK estates on 2026-07-27: each with its evidence, its consequence for a cons