opschain packs
Included from Basic tier
The local pack cache: the repo-scoped verbs that let a local run
(opschain run, runs create … --local) mount packs a repository
declares by git source — remote: or url: with rev: in
.opschain/packs.yaml — without a server and without the network at run
time.
A local run never contacts a remote: the packs it mounts come from the
release's bundled snapshot, from a signed bundle file (bundle:), or
from this cache. packs fetch is the one deliberate network step: it
resolves each git-sourced declaration to an exact commit through the
home's git mirrors, caches the tree under <opschain home>/packs/<name>/<sha>,
verifies a pack manifest the tree carries against the product keyring
and the local entitlements, and records the resolution in the pack's
cache index. Every later local run mounts that commit offline until you
fetch again.
The server's pack lanes are a different thing: a server resolves git
packs through the project's configured git remotes and pins them on the
template version or the run (opschain docs pack-store), and its
installed store of uploaded signed bundles is opschain admin packs.
| Subcommand | Purpose | Manual |
|---|---|---|
packs fetch | Resolve the repository's git-sourced pack declarations into the local pack cache | opschain docs cli/packs-fetch |
See also
opschain docs cli/packs-fetch— the verb, its refusals and the cache layout.opschain docs cli/admin-packs— the server's installed pack store.opschain learn 2.4— using packs;opschain learn 2.6— the local development loop.