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

The commands below point at the current release (v1.1.0). Linux and macOS require curl and Python 3; Windows uses PowerShell. No separately installed Cosign is required: the installer verifies the tag-pinned digest of agent-comms-verify before using it to check the release signature (see Verify a release).

Linux and macOS

curl -fsSL "https://raw.githubusercontent.com/DhanushSantosh/AgentComms/v1.1.0/install.sh" | AGENT_COMMS_VERSION=v1.1.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/v1.1.0/install.ps1" -OutFile install.ps1
.\install.ps1 -Version v1.1.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

The current release installer also places agc, a shorter synonym for agent-comms (agc version and agc tui work identically). The commands in these docs use the full name for clarity. If you manually replace a Windows dev binary instead of running the installer, keep agc.cmd beside agent-comms.exe or recreate it as described in Build from source.

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, running agent-comms update is the faster way to pick up a new release than re-running the installer — it checks first and prompts before installing, or pass --yes to skip the prompt.

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 v1.1.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
git switch dev
version="$(git describe --tags --abbrev=0 | sed 's/^v//')-dev"
go build -ldflags "-X github.com/DhanushSantosh/AgentComms/internal/app.Version=$version -X github.com/DhanushSantosh/AgentComms/internal/buildinfo.Version=$version" -o ./bin/agent-comms ./cmd/agent-comms
./bin/agent-comms version

./bin/agent-comms is a working binary built from the checked-out dev commit. It has no verifiable release signature of its own — it wasn’t produced by the signed release process — but agent-comms update is present and functional even here: it checks against and can replace this binary with an actual signed release, verified the same way the installer verifies one. For Windows PowerShell build commands and the optional agc.cmd shim, see CONTRIBUTING.md.