opschain academy show
packs:academy
opschain academy show
Reports three things: the Academy Server and channel this build
resolves the agent through, with the agent release it pins (the floor
the server lane accepts and the digest the file lane verifies) and
whether it carries a digest for this platform; the installed agent —
version, digest, origin (server:<url> or file:<path>), install time,
path and the version the agent itself reports; and the launch
configuration academy serve would use — the
targeted OpsChain server, where the credential comes from (login for
your stored opschain login session, environment for
OPSCHAIN_ACADEMY_TOKEN) and the agent's data directory. The credential's
value is never printed. When the launch cannot be resolved (local mode, no
credential) the reason is shown instead.
$ opschain academy show --server https://ops.example.com
Academy Server: https://academy.limepoint.com (stable channel) — `academy install` resolves the agent through it
Pinned release: v0.3.0 (LimePoint/opschain-academy-agent) — academy-opschain-agent_0.3.0_darwin_arm64.tar.gz; the floor the server lane accepts, the digest the file lane verifies
Installed: academy-opschain-agent v0.3.0 (sha256 3f1c…) from server:https://academy.limepoint.com at 2026-11-07T10:00:00Z
path: /Users/me/.opschain/academy/bin/academy-opschain-agent
agent version: v0.3.0
Launch: server https://ops.example.com, credential from login, data directory /Users/me/.opschain/academy
-o json / -o yaml emit the document: pinned (version,
repository, platform, archive, server, channel), installed
(null when none; a server install also carries channel, sdk_version,
server and signing_key_id), agent_version, launch (server,
token_source, data_dir) or launch_error.
Exit codes: 0 always when the install record is readable; 1 when it is corrupt.
See also
opschain docs cli/academy-install— install through the Academy Server, or from a file.opschain docs cli/academy-serve— run the agent.