Tuist's Elixir integration can now reuse compiled dependencies through the same Kura REAPI cache as Bazel. Enable it with cache: true and the compile alias to automatically select supported dependencies. Declare additional compile-time inputs or exclude dependencies with non-deterministic compilation when needed. An input key maps to an ActionResult referencing a content-addressed dependency compilation bundle; clean builds can restore it without compiling that dependency again. Authentication, endpoint discovery and signed cache analytics use the existing shared APIs.
The Mix Cache page follows Xcode's layout, showing average and percentile build hit rates above Recent Builds. Transfer, latency and throughput retain real measurements and local-copy/remote-CAS provenance; legacy values stay unavailable rather than zero. Each build's Mix cache tab has task hits, misses, hit rate and download/upload totals, a lookup breakdown, latency percentiles and searchable task rows with copyable keys and Xcode-aligned CAS-only expanded rows. Expand tasks to follow their actual bundle hashes into CAS Outputs, whose graph, download/upload throughput and output table use Bazel's shared REAPI queries over Kura-signed records. Local copies never become invented remote output rows. Bypassed and already-current dependencies do not count as misses; avoided compilation time is an estimate, not elapsed build savings.
Caching remains opt-in and dependency-only. Unsupported native/custom compilation falls back to Mix. A verified local snapshot store covers unavailable remote endpoints, authentication and storage failures without hiding compiler errors. Checkout paths participate in keys by default; portability requires explicit opt-in because BEAMs can retain producer paths. Compilation bundles can also embed compile-time values, so audit selected dependencies and project cache access. See the Elixir cache guide for configuration and safety limits.