Skip to main content

Installing

Three install paths. Pick whichever fits your machine — all three produce the same declaragent binary on your $PATH.

Since 0.4.1, a second alias d9t is installed alongside declaragent — same launcher, same flags, shorter to type. Use either.

curl -sSL https://get.declaragent.dev | sh

The installer:

  1. Detects (os, arch) — Linux x64, Linux arm64, macOS x64, macOS arm64.
  2. Downloads the matching tarball + .sha256 from the GitHub release.
  3. Verifies the checksum.
  4. Extracts declaragent into $HOME/.local/bin (overridable via DECLARAGENT_PREFIX).

Environment knobs:

VariableDefaultPurpose
DECLARAGENT_VERSIONlatestPin to a tag. Example: v0.7.6.
DECLARAGENT_PREFIX$HOME/.localInstall prefix. Binary lands at $PREFIX/bin/declaragent.
DECLARAGENT_BASE_URLGitHub releasesRelease mirror. Used by CI smoke tests against staging.
DECLARAGENT_NO_CHECKSUMunsetSkip the SHA-256 verify. Never advised.

The installer source lives at scripts/install.sh in the repo.

Verify

declaragent --version
# declaragent 0.7.6

# The d9t alias works the same way:
d9t --version
# declaragent 0.7.6

If the binary is on your $PATH and prints a version, you're done. Next: your first agent.

Troubleshooting

  • If the postinstall failed (npm path), re-run it by hand:
    cd $(npm root -g)/@declaragent/cli
    node bin/postinstall.js
  • If the curl installer bailed with a checksum mismatch, retry — transient CDN corruption is the usual culprit. Don't set DECLARAGENT_NO_CHECKSUM.
  • See Troubleshooting → my install failed for the flowchart.
Windows

There is no Windows-native binary yet — run under WSL2, or use the npm-global install path.