Build details now group toolchain versions, host information and runtime observations in one collapsed-by-default Build environment card below Build Details across Xcode, Gradle, Bazel, Mix, Cargo and Once. A compact, responsive key/value grid matches the layout of Build Details. Existing fields such as Gradle/Java, Xcode/macOS, Elixir/OTP, Rust, Bazel and Once versions appear alongside recognized properties such as available logical processors, Gradle worker limits, JVM heap limits, reported OS memory, operating system, process architecture and CI environment. Once uses its already-recorded version and host class without new collection. Memory and heap values are formatted for readability, while unknown properties remain in Custom metadata inside Build Details. Invocation settings, results and source information stay in Build Details.
Updated clients can collect these observations for Gradle builds, Mix compile reports, Cargo builds and live tuist xcodebuild build runs, when available and supported by the server. Imported Xcode activity logs do not acquire observations from the machine uploading them.
Your existing tags and custom values continue to work. Explicit values take precedence over automatically collected observations, and the same string-valued metadata is available through the API and Model Context Protocol tools, so agents can inspect the context behind a slow build too.
Runner names require explicit opt-in. Automatic collection does not include usernames, hostnames, network addresses or environment dumps. Reported properties describe the build environment; they are not verified runner identities.