Skip to content

AGP Community Edition v0.0.12

Choose a tag to compare

View all tags
@getraksha-ops getraksha-ops released this 21 Jun 02:50
v0.0.12
b450c29

AGP Community Edition v0.0.12 (private test release)

Pre-release build for private testing. The first public release will be v0.1.0.

Added

  • agp update — self-update the CLI. agp fetch installs the service
    binaries but never the CLI itself, so until now upgrading agp meant re-running
    the installer. agp update downloads the latest CLI release, verifies its
    SHA-256, smoke-tests that it runs, then atomically swaps it in — keeping the
    previous binary until the new one is validated and in place. It refuses to
    downgrade (--version vX.Y.Z for an explicit/rollback install; --check to
    only report availability). Not yet available on Windows — re-run install.ps1
    there. (Note: agp update works from v0.0.12 onward; users on v0.0.11 or
    earlier update the CLI once via the installer to pick it up.)

Changed

  • Out-of-the-box default ports. Fresh installs now bind the quiet
    27860–27868 (HTTP) / 27880–27885 (gRPC) range instead of common dev ports,
    so agp init + agp start work without conflicts on a typical machine. The
    console moves to http://localhost:27868 on new installs. agp init writes
    every service's listeners and its dependencies' addresses and the CLI
    profile endpoints from one computed topology, so they stay consistent — edit a
    port in one ~/.agp/services/<service>.env and agp restart it, or
    agp init --force to re-render every .env from defaults (keeps a .bak;
    secrets are never regenerated).
  • CLI config hardening. The CLI config (config.yaml) is now parsed with a
    standard YAML library and is created once by agp init and never overwritten
    by agp — not even with --force — because it accrues your agents and
    credentials over time. A config that exists but won't parse now produces a
    clear warning instead of silent misbehavior. JSON output is pretty-printed by
    default (--no-pretty for compact).
  • agp identity delete-agent permanently deletes an agent rather than
    decommissioning it.

Fixed

  • Identity: agent list filters. SQLite list-agents bound its filter
    arguments before pagination, so --status and --team-id filters now match
    the generated placeholders and return the correct rows.

Changed components vs v0.0.11: agp-cli (agp update, default ports, config
hardening, delete-agent) and agp-identity (the list-filter fix). All other
components carry the same commits as v0.0.11.

Upgrading from v0.0.11

agp fetch all
agp restart all

To update the CLI binary itself, re-run the installer (the agp update command
ships in this release, so v0.0.11 users pick it up on the next upgrade):

curl -fsSL https://raw.githubusercontent.com/getraksha/agp/main/install.sh | sh   # macOS/Linux

From v0.0.12 onward, agp update does this for you.

Existing installs are not disrupted: agp init is idempotent and never
rewrites your config.yaml, so your current ports and console URL stay as they
are. The new 27860+ defaults apply only to fresh installs.

Install

  • macOS / Linux: curl -fsSL https://raw.githubusercontent.com/getraksha/agp/main/install.sh | sh
  • Windows (PowerShell): irm https://raw.githubusercontent.com/getraksha/agp/main/install.ps1 | iex

Then agp init · agp fetch all · agp start all · agp setup --agent-id my-agent --client claude-desktop.

Platforms

macOS (arm64, amd64) · Linux (amd64, arm64) · Windows (amd64, arm64)

Verify

All assets are listed with SHA-256 checksums in SHA256SUMS and manifest.json; the CLI and install scripts verify checksums automatically.

Assets 64
Loading