Install Agent Comms

The installer places the CLI at user level. Existing managed projects reconcile themselves when the new binary first opens them; you do not copy a binary into every repository.

Before installation

Nothing to install first. The commands below already point at the current release (v0.6.0) — copy, paste, and run. The installer verifies the tag-pinned digest of agent-comms-verify before using it to check the release signature; no separately installed Cosign is required (see Verify a release). Linux and macOS also require curl and Python 3.

Linux and macOS

curl -fsSL "https://raw.githubusercontent.com/DhanushSantosh/AgentComms/v0.6.0/install.sh" | AGENT_COMMS_VERSION=v0.6.0 sh

The default destination is ~/.local/bin/agent-comms. Ensure ~/.local/bin is on PATH.

Windows PowerShell

Invoke-WebRequest "https://raw.githubusercontent.com/DhanushSantosh/AgentComms/v0.6.0/install.ps1" -OutFile install.ps1
.\install.ps1 -Version v0.6.0

The default destination is %LOCALAPPDATA%\Programs\AgentComms. The installer adds that directory to the user PATH when needed.

Confirm the active build

Open a new terminal and run:

agent-comms version
agent-comms update check

Starting with the next release after v0.6.0, the installer also places agc, a shorter synonym for agent-comms (agc version, agc tui, and so on work identically once it’s installed) — see the changelog for exactly which release. The commands on this page target v0.6.0, which does not yet install agc; every example in these docs uses the full agent-comms name regardless.

Installation preserves the previous binary as agent-comms.previous or agent-comms.exe.previous. Release assets are checked against SHA-256 and a Sigstore bundle before replacement. Running the installer again upgrades in place; once installed, agent-comms update apply is the faster way to pick up a new release than re-running the installer.

Installing a different release

Standalone installers deliberately do not resolve mutable stable or preview channels — the commands above always target one exact, protected tag. To install an older release or a preview instead of the current one, pick its tag from the release page and substitute it for v0.6.0 in either command above.

Build from source

Want dev’s current tip rather than a numbered release — to try something not out yet, or to run a binary you built yourself instead of trusting a download? No installer, no signature to verify, just Go:

git clone https://github.com/DhanushSantosh/AgentComms.git
cd AgentComms
go build -o ./bin/agent-comms ./cmd/agent-comms
./bin/agent-comms version

./bin/agent-comms is a real, working binary built from whatever commit you cloned — dev’s current tip by default. It has no verifiable release signature of its own — it wasn’t produced by the signed release process — but agent-comms update check/update apply are present and functional even here: they check against and can replace this binary with an actual signed release, verified the same way the installer verifies one. Building the other shipped binaries, contributing changes back, and the project’s development rules are in CONTRIBUTING.md.