Optional Claude Code bundle

All bundles

bundles/claude supplies the official stable Linux AMD64 and ARM64 Claude Code prebuilt with its own catalog, lock, carrier image, volume and /opt/bdock/claude root. Its 2.1.296 pins are retained unchanged from the original toolbox split. The source toolbox no longer includes this agent.

Published bundle

Version: 2.1.302-b1

Index digest: sha256:54b0ccca4a82aec31ffc6fd52ed00a3ce4aa8fb91dbcc0f437a7cb91d5102a4d

Source: 18cc0584b92d1ec3f01801b66431debd9eac4f2c

Publication: run 39123398012, attempt 1

Pull this published carrier by its immutable index digest:

docker pull quay.io/bundledock/claude@sha256:54b0ccca4a82aec31ffc6fd52ed00a3ce4aa8fb91dbcc0f437a7cb91d5102a4d

The source inventory below describes the current lock; this publication retains its exact source revision.

The official 2.1.296 manifest , checked October 12, 2026, identifies the linux-x64 and linux-arm64 raw executables and confirms both publisher SHA256 values copied from the toolbox. The complete executable, including any embedded notices, is retained unchanged as bin/claude. The builder verifies the downloaded binary checksum before installation. Native offline version invocation was subsequently checked on both architectures in the publication recorded above.

The carrier includes the unmodified upstream LICENSE.md from the exact pinned tag and a factual SOURCE notice . The upstream notice links Anthropic Commercial Terms .

Manual consumer use

The verified publication above supplies the carrier image. Consumer activation remains a separate operation requiring explicit approval. To initialize an image-derived volume from the verified carrier:

bdock tools volume --image quay.io/bundledock/claude@sha256:4b02222a4954f174a46af2a7ef732c2f0ff7b7bb7b462875491dd80aabf1940f --bundle claude

Mount the printed bundledock-claude-<full image ID> volume read-only at /opt/bdock/claude and prepend /opt/bdock/claude/bin to the consumer’s PATH. Use a stock glibc language image, such as the existing Debian Trixie Go consumer. The scratch carrier initializes volumes; it supplies no interactive runtime system libraries. Compatibility beyond this consumer remains unverified.

Keep HOME, caches, credentials, projects and existing agent configuration in writable consumer storage outside the immutable mount. Existing user filenames and settings pass through unchanged; BundleDock writes no user configuration. Set DISABLE_UPDATES=1 and DISABLE_AUTOUPDATER=1 in the consumer, following the existing toolbox convention. Carrier environment values do not transfer through a mounted volume. Authentication and network services remain the consumer’s responsibility; the smoke script only checks offline version invocation.

Updates, publication and evidence

bdock tools upgrade --directory bundles/claude updates this bundle alone. The propose-upgrades.yml workflow runs daily at 06:50 UTC, supports manual dry runs by default and proposes only its lock and generated source inventory through the shared updater. It never builds or dispatches native publication.

publish-bundles.yml uses the shared publication workflow . Initial native builds and publication require explicit manual approval of the full source SHA. Future eligible lock-only updater proposals follow the same actual human wstein merge, exact merged-main CI and frozen-lock publication flow as the other bundles. The separate destination is quay.io/bundledock/claude; the verified initial publication is recorded above. Registry visibility and robot permissions were verified for that operation. Successful approved publication creates an annotated claude/<immutable-version> source tag after verified promotion. Consumer activation is a separate operation.

Source fixtures cover singleton checksum-verified fixture installation, both architecture catalogs, copied notices and fake Docker orchestration with repeated initialization and two read-only non-root consumers. The extraction and volume integrity checks use the existing generic profile. The publication above also completed native Linux AMD64 and ARM64 builds and offline consumer smoke checks, followed by verified index/alias promotion and the annotated source tag. Its workflow failed only in the subsequent documentation source proposal because this guide lacked publication markers; the receipt records the completed publication. Vulnerability scans and consumer activation remain unverified.