mait.sh1.69.2

Private beta: features and content may change. No warranty; use at your own risk.

Docs / Launcher and command-line tools

AIDC Pack

Package a specific tool version for AIDC distribution, with an archive and manifest you can inspect before publication.

For toolchain maintainers and release engineers publishing packages consumed by AIDC.

Read from the top for the basics; the later sections go deeper.

Beta
All components

What it doesBasics

  • Isolated package capture
  • Shared-library bundling for Python, Ruby, and PHP
  • BLAKE3 integrity checks
  • Package inspection
  • Resumable authenticated publishing

First useBasics

  1. Build and inspect one tool package before deciding whether to publish it.
  2. Inspect and verify the generated package.
  3. Publish it for signed distribution through the configured channel.

Everyday tasksEveryday use

Publish a verified tool package

A release engineer needs to add a tool version to the package channel used by reproducible workspaces.

  1. Select the tool identity and target platform and architecture, then capture from its verified source.
  2. Inspect the generated package and manifest for expected commands, files, size, and target identity.
  3. Run package verification before any upload.
  4. Publish through the authenticated channel; confirm whether the Hub signature was retrieved into the local manifest.

What you getThe channel receives an artifact whose contents and identity were checked before publication.

How to check: Build, inspect, and verify reports plus successful chunk completion identify the artifact, and a retrieved Hub signature stored locally adds further evidence.

Recover a large package upload

A large tool distribution is interrupted during publication and should not restart from its first byte.

  1. Keep the verified local package and manifest unchanged after the interruption.
  2. Confirm channel, credentials, target identity, chunk size, retry policy, and timeouts.
  3. Repeat publication so the hub reports already accepted chunks and upload resumes from the remaining range.
  4. Verify completion. If signature retrieval warned after successful publication, rerun the unchanged publish so upload is skipped and retrieval is retried.

What you getPublication continues from verified chunk state instead of rebuilding or re-uploading the entire artifact.

How to check: Resume status identifies accepted chunks and each remaining chunk passes BLAKE3 verification; final metadata matches the package, with a local signature recorded when retrieval succeeds.

Settings to decideAdvanced

Choose isolated or direct capture
Use Docker capture for the normal isolated, reproducible path. Select direct capture only in a controlled build environment that intentionally owns the local AIDC installation state.
Declare target platform and architecture
Set the package target independently from the machine running AIDC Pack, and preserve the same target identity through build, inspect, verify, and publish.
Choose durable package storage
Use a storage path with capacity for captured files, package output, and manifests. Retain unchanged artifacts when an upload must resume.
Tune chunking and timeouts for the artifact
Keep bounded retries and choose chunk and timeout values appropriate to artifact size and network conditions, and fix identity or integrity failures at their source.

CommandsAdvanced

$ aidc-pack version
$ aidc-pack build nodejs 22.21.1
$ aidc-pack inspect nodejs 22.21.1 --files
$ aidc-pack verify nodejs 22.21.1
$ aidc-pack publish nodejs 22.21.1

Problems and fixesHelp

What you seeCheckFix
Build cannot capture the requested tool installation.Confirm the tool version and distribution exist, vendor verification succeeds, the capture backend is available, and the target has enough storage.Correct the source or capture environment and rebuild from a clean target directory.
Verification reports missing commands, runtime keys, checksums, or unresolved dependencies.Inspect the package manifest and file listing against the tool’s expectations and requested target.Fix the capture or portability issue, rebuild the package and verify it again before publication.
Publication stops on authentication, timeout, or exhausted chunk retries.Separate credential or channel errors from transient chunk transport errors and confirm the local artifact has not changed.Refresh authenticated access when needed, adjust bounded transport settings for known network conditions, and resume the unchanged artifact. If only signature retrieval failed, rerun the same publish without rebuilding.
What you see
Build cannot capture the requested tool installation.
Check
Confirm the tool version and distribution exist, vendor verification succeeds, the capture backend is available, and the target has enough storage.
Fix
Correct the source or capture environment and rebuild from a clean target directory.
What you see
Verification reports missing commands, runtime keys, checksums, or unresolved dependencies.
Check
Inspect the package manifest and file listing against the tool’s expectations and requested target.
Fix
Fix the capture or portability issue, rebuild the package and verify it again before publication.
What you see
Publication stops on authentication, timeout, or exhausted chunk retries.
Check
Separate credential or channel errors from transient chunk transport errors and confirm the local artifact has not changed.
Fix
Refresh authenticated access when needed, adjust bounded transport settings for known network conditions, and resume the unchanged artifact. If only signature retrieval failed, rerun the same publish without rebuilding.

All AIDC Pack problems and fixes →

Good to knowHelp

  • AIDC Pack runs on supported Linux hosts and can also target supported Darwin identities.
  • Standard tools use AIDC source verification; Android components use their documented sdkmanager capture path.
  • Rerunning an unchanged publish retries the local signature fetch.