Skip to content

AGP Community Edition v0.0.11

Choose a tag to compare

@getraksha-ops getraksha-ops released this 19 Jun 18:48

AGP Community Edition v0.0.11 (private test release)

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

Fixed

  • Windows: policy no longer denies every tool call. On Windows the policy
    engine loaded its bundle from an absolute temp directory, and OPA's directory
    data-mounting silently failed for an absolute path — leaving the tool
    classification data unmounted, so every governed tool was denied with
    "No matching policy" even when registered and granted. The engine now reads
    the bundle's .rego modules and data.json files directly and serves the data
    from an in-memory store, which behaves identically on macOS, Linux, and
    Windows. The bundle also degrades gracefully (missing data = "no overrides"
    rather than a blanket deny), and the engine now fails to start loudly if a
    plain read tool does not classify — so this can never ship silently again.

Changed

  • Uniform /health contract and version stamping across identity, registry,
    behavior-profile, audit, approval, proxy, the shared proto, and the CLI:
    services report their build version on /health/live, surfaced by
    agp status.

Changed components vs v0.0.10: agp-policy (the Windows fix) plus the health/version
work above. agp-admin-ui, agp-shared, and agp-mcp-servers carry the same
commits as v0.0.10.

Upgrading from v0.0.10

agp fetch all       # macOS/Linux
agp restart all

On Windows: agp fetch all then agp restart all. Windows users on v0.0.10
should upgrade — this release is what makes governed tool calls work there.

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.