Skip to content

Releases

v0.9.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 17:03

Changes

Added

  • A catalog publish refuses a Component version no Recipe realizes while the version below it has Recipes.
  • The assistant set-up page has a Claude Desktop section: install on your computer, connect through the extension package.

Fixed

  • aggrega import --sync re-imports a folder you have built without --format: the build's dist/ folder is not read.
  • The task examples resolve core/compute/task 1.0.1 again, so a fresh pull finds Recipes for it.
  • The editor's aggrega.server.binaryPath accepts ~/… and ${userHome}, and a failed start names the path it tried.
  • The editor's Commands panel shows the attached workspace and Release after being hidden, and re-choosing the current workspace says so.

Install

These commands install this release, 0.9.1.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.1/install.sh | AGGREGA_VERSION=0.9.1 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.1'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.1/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.1-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.1-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.1-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.1-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.1-windows-amd64-setup.exe Windows installer
aggrega-0.9.1.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
quickstart-ai.sh, quickstart-ai.ps1, quickstart-web.sh, quickstart-web.ps1 Quickstart scripts: each runs one step of an example from the documentation
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 08:07

Changes

Aggrega 0.9.0, the first public release. It brings the aggrega.ai/v1beta1 schema.

Documents, schemas, plugins and published artifacts now use aggrega.ai/v1beta1, which changes only additively, and from this release on Aggrega promises compatibility for schemas, commands, flags, assistant tools, error codes and plugin kits, as the Compatibility page states.

Highlights

  • The aggrega.ai/v1beta1 schema, stable from here on: a document or plugin still on v1alpha1 is refused.
  • aggrega import turns a Langflow, Flowise, n8n, Dify, CrewAI, LangGraph, Agent Framework, Google ADK, MCP or Docker Compose project into a workspace you can build and deploy, in one command.
  • One command runs a quickstart: curl -fsSL https://aggrega.ai/quickstart-ai.sh | sh, or irm https://aggrega.ai/quickstart-ai.ps1 | iex on Windows.
  • Every quickstart, import and example page offers a prompt for your AI assistant and shows the project open in Visual Studio Code.
  • The Visual Studio Code extension aggrega-ai.aggrega speaks the documentation's languages and asks for the values an import still owes.

Added

  • aggrega import drafts a Release and a complete Manifest, asks once for what no source holds (--answers, by default import-answers.yaml), and pulls the drafted Release's dependencies; --offline skips the pull.
  • On Docker Compose, imported platforms and agents publish their port on 127.0.0.1 through published_port, and every walkthrough shows how to test it.
  • Dify, MCP servers run from an image, and the HTTP-request and retrieval tools deploy on Docker Compose; Dify sends nothing to its vendor unless a Release sets telemetry_enabled or marketplace_enabled.
  • The AI quickstart opens a chat page from its first step, and quickstart-web serves a page in the browser.
  • The aggrega-skills plugin installs in Claude Code, Codex, Cursor, Copilot, Gemini CLI, Antigravity, Kiro and OpenClaw.
  • A Windows installer installs Aggrega without administrator rights.
  • The language server and the assistant's import tool return owed values as owed and accept answers as answered.
  • The documentation has a Visual Studio Code section with screenshots, a Compatibility page and a public roadmap.

Changed

  • The plugin kits and ABI codecs follow semantic versioning; Go plugins import github.com/aggrega-ai/aggrega-pdk/go and github.com/aggrega-ai/aggrega-abi/go.
  • An import references the catalog component a source matches strongly, translates what the source states, and names its drafts after the source.
  • Catalog components running your own image deliver their values under default variable names, which an inject: block can rename.
  • Builds and first pulls are faster: dependencies are fetched in parallel and signatures are checked once per run.
  • Commands show progress while they wait, slow down when a registry is busy, and print only what concerns them.
  • A relative workspace_root on an assistant tool call is read from the Workspace folder, and scaffold returns the folder it wrote.

Fixed

  • Imported Langflow flows open in Langflow's editor with all their connections; Dify on Kubernetes starts and answers; LangGraph on Docker Compose waits for its store.
  • Kubernetes accepts names holding /; lockfiles keep same-named entities of different kinds apart; aggrega pull fetches the base a wrapper extends.
  • Refusals name what is missing and how to fix it, for unmapped Features, inject mistakes and credential Features a Recipe cannot deliver.
  • helm/k8s-existing-secret refuses an empty Secret name, and the installers and the build output print correctly on Windows and on terminals.

Install

These commands install this release, 0.9.0.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0/install.sh | AGGREGA_VERSION=0.9.0 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.0-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-windows-amd64-setup.exe Windows installer
aggrega-0.9.0.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
quickstart-ai.sh, quickstart-ai.ps1, quickstart-web.sh, quickstart-web.ps1 Quickstart scripts: each runs one step of an example from the documentation
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.9.0-rc.7

v0.9.0-rc.7 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Nov 18:50

Changes

Changed

  • A first build pulls faster again: the dependencies of a pull are fetched from the registry several at once.
  • Go plugins import the plugin kit from github.com/aggrega-ai/aggrega-pdk/go and the codec from github.com/aggrega-ai/aggrega-abi/go.

Install

These commands install this release, 0.9.0-rc.7.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.7/install.sh | AGGREGA_VERSION=0.9.0-rc.7 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0-rc.7'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.7/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-rc.7-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.0-rc.7-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-rc.7-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-rc.7-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-rc.7-windows-amd64-setup.exe Windows installer
aggrega-0.9.0-rc.7.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
quickstart-ai.sh, quickstart-ai.ps1, quickstart-web.sh, quickstart-web.ps1 Quickstart scripts: each runs one step of an example from the documentation
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.9.0-rc.6

v0.9.0-rc.6 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Nov 08:53

Changes

Added

  • The aggrega-skills repository installs as a plugin in Claude Code, Codex, Cursor, Copilot, Gemini CLI, Antigravity, Kiro and OpenClaw, adding the skill and aggrega mcp.
  • One command runs a quickstart step: curl -fsSL https://aggrega.ai/quickstart-ai.sh | sh, or irm https://aggrega.ai/quickstart-ai.ps1 | iex on Windows; quickstart-web likewise.
  • The AI quickstart opens a chat page in the browser from its first step, and quickstart-web serves a page for the browser.
  • With no catalog folder set, aggrega import fetches the hub's signed catalog snapshot, pins it, and refreshes it with --upgrade.

Changed

  • The set-up prompt for AI assistants installs the Aggrega plugin first, and falls back to the skill and a manual MCP connection.
  • The installers print a short, clean summary ending with the installed aggrega version and the next steps.
  • aggrega scaffold --list and the examples follow one teaching order, and every example page shows what aggrega scaffold prints.
  • Importers name their drafts after the source, and aggrega plugin gen-catalog writes no licence or copyright lines into your files.
  • A first build pulls faster: the trust root is fetched once per run, registry sign-ins are remembered, and signatures are checked several at once.
  • The LangGraph Compose Recipe 1.0.1 runs the quickstart agent 1.0.1 by default.
  • Comments in the files aggrega scaffold writes use plain ASCII, so they read correctly in Windows PowerShell.
  • The copyright holder is written Cognitio s.r.l.

Fixed

  • The quickstart agent leaves a refused or failed turn out of its conversation, so the next turn is answered.
  • install.ps1 prints the version line's em dash correctly in Windows PowerShell 5.1.
  • The editor no longer shows diagnostics from a validation of older text or from one cancelled partway.

Install

These commands install this release, 0.9.0-rc.6.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.6/install.sh | AGGREGA_VERSION=0.9.0-rc.6 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0-rc.6'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.6/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-rc.6-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.0-rc.6-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-rc.6-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-rc.6-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-rc.6-windows-amd64-setup.exe Windows installer
aggrega-0.9.0-rc.6.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
quickstart-ai.sh, quickstart-ai.ps1, quickstart-web.sh, quickstart-web.ps1 Quickstart scripts: each runs one step of an example from the documentation
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.9.0-rc.3

v0.9.0-rc.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 11 Nov 16:34

Changes

Added

  • Anyone can read what the hub, hub.aggrega.ai, publishes without a login; publishing to it still needs credentials.
  • Every import walkthrough ends by running what the build wrote and showing it answer a request.
  • A Windows installer installs Aggrega without administrator rights, through a wizard offering the install folder, an Add to PATH choice and the next steps.
  • The daemon's plugin-add answer carries withdrawn: true when the version you named has been retracted, as the command line says.

Changed

  • Documents, schemas, plugins and published artifacts use aggrega.ai/v1beta1, which changes only additively; a document or plugin still on v1alpha1 is refused.
  • Releases promise compatibility from 0.9.0 for schemas, commands, flags, assistant tools, error codes and plugin kits, as the new Compatibility page states.
  • The plugin kits and ABI codecs follow semantic versioning from 0.9.0, and a change breaking their API ships only in a new minor version.
  • Catalog components running your own image deliver each own value under a default variable name, which a component-level inject: block can rename; Recipes read .context.self_inject.
  • An inject block naming a mechanism all is refused with its reason, and a schema not branch's own description is printed as its refusal.
  • Importing a folder no importer recognises suggests importing one of its files, or naming a format whose importer reads folders.
  • A build whose catalog holds no parser for a format reads it through the compiler's built-in parser, as an import does.
  • Commands show progress while they wait, print the workspace warning only where it applies, and plugin add cli <name>[:<version>] works outside a workspace.
  • Commands wait as long as a busy registry asks, send it fewer requests at once, and stop by name after five minutes of slow-down answers.
  • LangGraph Recipes hand the graph its recursion limit, its checkpointer store's password, and the store's user and database where it publishes them.
  • The Claude Desktop package runs the aggrega on your PATH and asks you to set an empty Workspace folder.

Fixed

  • Kubernetes accepts builds whose Aggregate name or environment holds /; the label is rewritten and the exact value kept as an annotation.
  • An unmapped Feature's refusal lists the FeatureRecipes implementing its type for the component's target, or those for other targets when none fits.
  • With no catalog directory, the refusal for an unmapped component or Feature says it searched only the lockfile's pins.
  • Lockfiles record each entity's kind, keeping same-named entities of different kinds apart, and pull --detail names each kind correctly.
  • aggrega pull fetches and pins the base a Component or Feature extends, so wrappers build and validate without mapping their base.
  • A governance plugin at a label or annotation transform role builds from the hub with no catalog directory.
  • A verdict policy naming another release of a built-in governance plugin runs the compiler's own engine.
  • A Feature attachment's inject entry written with value: is refused; write the literal in the component's own block.
  • An attachment inject entry whose from: names a key its FeatureRecipe does not publish is refused, unless the FeatureRecipe reads .inject itself.
  • A refusal whose own sentence quotes nothing sensitive is printed, and the duplicate-delivery-key refusal says how to give each attachment its own key.
  • Helm compute Recipes refuse a credential Feature they cannot deliver, by name, and Helm secret realizations refuse a Compose-style ${…} origin.
  • Import drafts describe LangGraph images and =Env. references correctly, name Agent Framework MCP servers in comments, and leave non-Gemini ADK models unwired.
  • The Google ADK import's draft header says ADK also serves some providers' models, such as claude-… and gpt-… names, through classes of its own.
  • Dify built for Kubernetes starts every service, stays up and answers requests; its import step prints Dify's refusal and stops retrying.
  • The Dify plugin runtime and LangGraph Compose Recipes run no shell syntax and accept quotes in a connected store's address.
  • On Docker Compose, a LangGraph graph starts once its store accepts connections.
  • Langflow on Docker Compose can write to its data volume, and Ollama defaults to 0.15.6, serving the Responses API.

Install

These commands install this release, 0.9.0-rc.3.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.3/install.sh | AGGREGA_VERSION=0.9.0-rc.3 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0-rc.3'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.3/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-rc.3-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.0-rc.3-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-rc.3-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-rc.3-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-rc.3-windows-amd64-setup.exe Windows installer
aggrega-0.9.0-rc.3.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.9.0-rc.2

v0.9.0-rc.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Nov 08:16

Changes

  • Nothing a user can see changed since 0.9.0-rc.1; this candidate corrects one of the checks the release runs on each platform.

Install

These commands install this release, 0.9.0-rc.2.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.2/install.sh | AGGREGA_VERSION=0.9.0-rc.2 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0-rc.2'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.2/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-rc.2-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.9.0-rc.2-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-rc.2-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-rc.2-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-rc.2-windows-amd64-setup.exe Windows installer
aggrega-0.9.0-rc.2.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.8.11

Choose a tag to compare

@github-actions github-actions released this 06 Nov 16:08

Changes

Added

  • The documentation, catalog and home sites are now published in Italian, German, French, Spanish, Brazilian Portuguese and European Portuguese.
  • The home page explains how Aggrega works with translated diagrams and icons, and the documentation adds diagrams of Features, roles and AI gateways.
  • A plugin diagnostic's location can name the component it concerns in a new instance field, kept apart from uri, which names a document.
  • A new Import section teaches aggrega import, with a walkthrough for every format it reads that takes a project to a build.
  • Getting started and two examples now show diagrams of how Aggrega works, of one application on many platforms, and of build-time policies.
  • The import walkthroughs build as written, say where to clone the standard-library catalog, and run CrewAI and LangGraph on Docker Compose.

Changed

  • Compose sidecar and init services are now named <component>--<container>, so containers of different components no longer share a name; existing ones are recreated.
  • Catalog credential slot descriptions now name the development value a Recipe uses when the slot is unattached, a value every such Release shares.
  • A diagnostic about one component now names it as (instance <name>) after the file, or instance <name> alone, never where a file belongs.

Fixed

  • Imported drafts build without hand repair: each connection gets its own alias, Langflow's OpenAI model is wired, and drafted Releases place every model and datastore.
  • aggrega import uses its built-in importer when the catalog holds importer entries without their module, and a registry refusal says to re-run the import.
  • Compose builds of CrewAI, LangGraph and PostgreSQL accept a credential that only the Release attaches.
  • aggrega validate <entity> and the assistant's catalog:// resource now name the broken catalog file skipped at load instead of only reporting the entity not found.
  • The RDS Recipes now document subnet_group, parameter_group and vpc_security_groups as override keys shared across AWS Recipes, not Terraform argument names.
  • A Recipe with source: "" is now refused when loaded, so pull, build and validate all report E0251, advising to omit or fill the field.
  • aggrega validate now refuses a Component or Feature whose socket or slot selector cannot be parsed, even when nothing wires that socket or slot.
  • aggrega lint <plugin.yaml> now reads the .wasm beside the entity, where guest builds now write it, and notes what the entity leaves undeclared.
  • An empty inject: {} on an attachment filling a slot that permits no delivery now builds inside imported modules and subsystem-wide attachments too.
  • A boundary's subDirectory: "{{ .component_id }}" now names a boundary-scope Feature attachment's folder after its aggrega.ai/component-id label, not an internal marker.
  • aggrega inspect, aggrega validate --release and the assistant's matching tools now refuse an out-of-date lockfile with the build's E0130 halt.
  • A template reading .inject_raw now sees a component's custom inject mechanisms, such as ssm_param, beside env, file and arg.
  • A FeatureRecipe's valuesMapping now reads its own source: at .source, never the source of the component it is attached to.
  • aggrega registry update shows its progress while it walks a registry, as build and pull do.
  • In the editor, a Manifest mapping fault now appears on the Manifest, at the faulty mapping entry, instead of on the Aggregate.
  • The Strimzi and RabbitMQ operators are now workers: broker sockets refuse them at validate, while Prometheus's scrape_target, core/prometheus-exporter and core/caller-allowlist accept workers.
  • With nothing attached to its backend credential, Langfuse now presents the catalog's development database password and can sign in to a catalog PostgreSQL.
  • Helm builds now refuse a component name giving a CronJob over 52 characters or a Service over 63, and shorten a Feature attachment's name instead.

Install

These commands install this release, 0.8.11.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.11/install.sh | AGGREGA_VERSION=0.8.11 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.8.11'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.11/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.8.11-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.8.11-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.8.11-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.8.11-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.8.11-windows-amd64-setup.exe Windows installer
aggrega-0.8.11.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.8.10

Choose a tag to compare

@github-actions github-actions released this 03 Nov 16:13

Changes

Added

  • Diagrams in the documentation are drawn, following the page's light or dark theme.
  • Builds now warn when an aggrega.ai/ annotation reaches a Terraform render, which applies none; provider plugins declare this with readsNoWellKnownAnnotations: true.

Changed

  • The catalog site's kind boxes open a filtered Browse, its filters live in the URL, and aggrega-ai's signed entities show as Official under one publisher.
  • A listed catalog directory that does not exist, or is not a directory, now halts every command reading the catalog, naming its configuration line.
  • Documentation examples list no catalog outside themselves, so a copy of the documentation alone builds them from the hub registry.

Fixed

  • On Docker Compose a service port publishes onto the container port it names; adminer keeps serving 8080 while infra.port sets its published or Service port.
  • aggrega build names each file in its output it did not write, in one warning, and counts them on its closing line; nothing is deleted.
  • A plugins.linter entry, or a verdict-role plugins.governance entry, naming a function: but no uri: now halts the configuration load, naming the entry.

Install

These commands install this release, 0.8.10.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.10/install.sh | AGGREGA_VERSION=0.8.10 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.8.10'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.10/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.8.10-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.8.10-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.8.10-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.8.10-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.8.10-windows-amd64-setup.exe Windows installer
aggrega-0.8.10.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.

v0.8.9

Choose a tag to compare

@github-actions github-actions released this 02 Nov 13:47

Changes

Added

  • Attach core/manual-trigger to a task to deploy it unstarted on Kubernetes, Docker Compose or Amazon ECS, and start each run yourself.
  • Back up through Velero, K8up, KubeStash, Kasten, CloudNativePG, mariadb-operator or AWS Backup, onto a bucket or a volume, with optional point-in-time recovery.
  • New examples: a task run on demand, and one datastore backed up on every target from a single core/backup attachment.
  • The documentation is published in Chinese, Japanese, Korean, Polish, Turkish, Ukrainian, Indonesian, Vietnamese and Russian, marked machine-translated, with a version selector by minor release.
  • aggrega.ai serves a home page introducing Aggrega, with links to the documentation and the catalog.
  • aggrega scaffold --example <name> writes a documentation example into a new folder, and --example --list lists them; the assistant and the editor can too.
  • The install scripts print the next steps, and --completion and --skills (-Completion, -Skills on Windows) also set up shell completion and the assistant skill.
  • The documentation opens with a Start here group: AI assistant pages with a translated set-up prompt, a Getting started page and a Learn Aggrega path.
  • Two quickstart examples, a LangGraph agent on a local model and a web app with PostgreSQL, grow step by step from Docker Compose.
  • The catalog runs core/compute/server, an agent and core/gateway/litellm on Docker Compose, with two published quickstart images under tools/.
  • The hub counts pulls per catalog entity version and records nothing about who pulled; the privacy page states what is counted.
  • Translated pages on every site say they are machine-translated, and each language picker names a language in your own language on hover.

Changed

  • helm/mariadb-cluster runs MariaDB replication from infra.ha, and helm/mariadb refuses infra.ha by name instead of ignoring it.
  • aggrega registry update re-reads only what changed, walks registries in parallel, retries failed reads rather than recording versions unsigned, and names unreadable repositories.
  • Code blocks in the documentation follow the light or dark theme, on a grey surface with syntax colours that are easier to read.
  • aggrega validate --release now evaluates Recipe and FeatureRecipe assertions against the Release's values, failing where aggrega build would.
  • The Start here pages live at /docs/ai-assistants/, /docs/install/ and /docs/learn/; their old /docs/authoring/ addresses redirect permanently.
  • Example READMEs give the aggrega build commands that work in a copy made with aggrega scaffold --example; ./build-release.sh stays for CI.
  • The documentation's language picker is a drop-down menu that works with the arrow keys and Escape.
  • The accessibility button floats at the bottom right of every page and no longer shortens the sidebars.
  • A pull fetches each manifest once, by the tag or digest it names, and checks its bytes against that digest.

Fixed

  • An unknown command now answers immediately from the local registry index, and says how to install or search for a CLI plugin of that name.
  • A value declared sensitive behind a $ref reference is now withheld from diagnostics, and a pillar written as a #/$defs/ reference publishes the definition's keys.
  • A connection's values and infra leaves its socket declares sensitive are now withheld from --ir-graph, the trace and governance plugins.
  • A refusal now withholds a declared-sensitive value read from inside a list, such as a boundary connection's provides or .context.used_by.
  • The trace now shows a component's .context.inject block when its only deliveries use a custom mechanism, withholding declared-sensitive values.
  • A credential holding a double quote or a backslash now reaches the rendered output intact through the standard catalog's credential Features and Recipes.
  • A FeatureRecipe injectMapping whose output cannot be read, or writes deliveries under all:, now halts the build naming the attachment, instead of silently delivering nothing.
  • A bare annotation value its binding cannot place halts with E0367 where written, and aggrega validate reports an unsupported workload input kind with E0265.
  • On Docker Compose, a volume mount's subPath now mounts that part of a persistent volume, and is refused by name on other volume kinds.
  • A sourced Docker Compose service keeps every label its file writes, in list form or with number and true/false values, beside the provenance labels.
  • An imported module's components now meet the inject: allowlist and delivery-key rules, and its subsystem and Release-written attachments may name only declared sockets.
  • A Feature an imported module attaches to one of its own subsystems now reaches the module's components there, and meets the Feature's appliesTo.
  • An annotation-transform policy and boundary annotation bindings now reach every component routed in through aggregates:, named or not, addressed by graph id like documents.backend.
  • Platform annotations such as aggrega.ai/namespace declared on an Aggregate subsystem or component, or in a module, now reach rendered output; the Release's value wins.
  • Registry access reports a malformed credential entry or config.json, and aggrega login and aggrega logout a malformed config.json, naming registry and file, never contents.
  • On Docker Compose, a credential attached to an external service, as on compose/twilio, is refused by name; its slots are optional there, required on Kubernetes.
  • A build reaching a Component or Feature whose extends: chain loops now halts with the cyclic extends chain error instead of crashing.
  • Diagnostics and lockfile references name top-level components at .spec.components; findings on imported module components point at the written key in the Release or module.
  • An imported module's attachment whose delivery its slot refuses now halts saying how to fix it, within the mechanisms a slot can declare.
  • compose/langflow and helm/langflow keep Langflow's data at /app/langflow, the directory its image creates, so Docker Compose volumes are writable by Langflow.
  • helm/langflow, helm/flowise and compose/flowise keep data writable by the non-root user current images run as; Flowise's data moves to /home/node/.flowise.
  • A pull's unfinished deprecation-marker lookup is now reported as a lookup that did not complete, with its reason, not as a marker not honored.
  • A schema library only the artifact cache holds is now named, with the action that works there, by validate, entity validation, pull and build --auto-pull.
  • The public catalog's Capability filter now lists each plugin's published capabilities, and plugin pages show their plugin type and drop two always-empty rows.
  • A reference that resolves to nothing now names any catalog file declaring an Aggrega apiVersion that does not parse, with the parser's reason.
  • The editor, the assistant's describe and validate, and inspect --closure now report a withdrawn plugin recorded in the plugin trust record, as the build does.
  • aggrega inspect prints a catalog Component as YAML under -o yaml, and draws extending Releases and Manifests as a build composes them.
  • aggrega deprecate --from and the daemon's aggrega/deprecateArtifact now refuse a severity, reason, replacement or message passed beside the batch file, instead of ignoring it.
  • An aggrega registry update stopped while writing an index now leaves it complete or absent, never a partial index shown as current.
  • A schema halt over content read through $import: now names the imported file beside its line, instead of the entity's file.
  • A top-level template field holding nothing renders empty; $. ranges match dot ranges; (.locals).key halts like .locals.key; printing and ranging unset paths halts.
  • On Docker Compose, the build now warns about a persistent volume's dropped class or accessModes, and a uses edge into a later sync wave.
  • Warnings for an inline x-aggrega-* schema keyword and for an unverified plugin now print once, untimestamped, beside a build's other warnings, and reach the editor.
  • A Recipe or FeatureRecipe whose pipeline repeats a step id is now refused with E0370, naming both steps' lines.
  • aggrega validate and aggrega lint halt with E0371 on a catalog file with a misspelled kind:, and builds name it when its entity is missing.
  • Managed database Recipes refuse a password attachment the cloud service would ignore, and PostgreSQL and MariaDB Recipes refuse infra.credentials settings they cannot honour.
  • A failed provides: entry now shows the condition that stopped it beneath E0056.
  • aggrega plugin add provider now writes provider/<name>, which the next pull resolves; an oci:// provider binding is refused naming the form to write.
  • A refused workspace configuration now reads "workspace configuration is invalid" instead of claiming a schema failure where the schema passed.

Install

These commands install this release, 0.8.9.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.9/install.sh | AGGREGA_VERSION=0.8.9 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.8.9'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.9/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.8.9-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/ar...

Read more

v0.8.8

Choose a tag to compare

@github-actions github-actions released this 30 Oct 03:17

Changes

Added

  • Boundary-scope FeatureRecipe templates can read .boundary.assembly_path, the directory their own output is assembled into.
  • A Compose service can list component ids under x-aggrega-networks-of to join those components' networks in its own compose file.

Changed

  • A FeatureRecipe's injectMapping reads the component it runs for at either execution scope, and a .boundary read in it halts the build.
  • A boundary-scope FeatureRecipe's locals and provides are evaluated once for its boundary, so every component reads the same values, .boundary reads included.
  • The build halts when a boundary-level Feature's compose or CloudFormation output would reach no assembled file, where it was dropped without a message.
  • The compose bridge sets a connection's host variable to aggrega-gw and its port variable to the listen port, relaying only within its own file.
  • Assertions read an authored number as value templates do: an authored 0 is empty to if and default, and 0.1 equals the literal 0.1.
  • Every model Component refuses a context_window below 1 when its values are validated; leave it out to keep the model's default.
  • The Plugin, Recipe, Workload and compact-form reference pages now describe the forms a build accepts and what gen-catalog records.
  • An entity lock names its ignore rules' plugin without a version, so re-pinning with another release leaves it unchanged; delete older locks and pin again.
  • Provider plugins no longer carry the compiler's WebAssembly runtime, halving most of them, and aggrega plugin run-local now starts the helm plugin.

Removed

  • Error E0322 is retired: a boundary-level Feature's provider plugin no longer rewrites consumers' environment; the compose bridge's own injectMapping does.
  • The provider render socket's boundary_env_overrides export and its two wire shapes are removed from the schema, the ABI codecs and the plugin kits.

Install

These commands install this release, 0.8.8.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.8/install.sh | AGGREGA_VERSION=0.8.8 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.8.8'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.8/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.8.8-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.

Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.

Files

Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):

File What it is
aggrega-0.8.8-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.8.8-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.8.8-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.8.8-windows-amd64-setup.exe Windows installer
aggrega-0.8.8.mcpb Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS
install.sh, install.ps1 Install scripts
SHA256SUMS SHA-256 of every other file; check with sha256sum -c SHA256SUMS

Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are not signed or notarized.