Agulater

Agulater is an optional lifecycle and package tool for Agul. It installs or updates Agul runtimes, manages Skills and Plugins, and compiles readable .agents packages into the small launch files Agul consumes.

Agulater does not run models, provide a TUI, or coordinate agents.

Do you need it?

• To run basic Agul: no. Use Agul's standalone binary or installer.
• To manage Agul versions or install AgentKube extensions: yes.
• To prepare a custom .agents package: yes.

Published Agulater releases are self-contained executables. Normal users do not need Bun, Node.js, or npm. The source tree is TypeScript and uses Bun only for development and release builds.

Install the first experience release

Install 0.2.1 using its pinned standalone installer.

Linux or macOS:

curl -fsSL https://github.com/storious/agulater/releases/download/v0.2.1/install.sh | sh

Windows PowerShell:

irm https://github.com/storious/agulater/releases/download/v0.2.1/install.ps1 | iex

These recommended install commands do not need Bun, Node.js, or npm.

The installer selects the current platform, installs agulater in a user bin directory, runs agulater setup user --if-missing, and adds that bin directory to the user PATH when needed. Pass --no-modify-path on Unix or -NoModifyPath on Windows to opt out. Setup preserves an existing ~/.agents package; for a new user it creates the general package and registers the AgentKube Catalog without downloading extensions.

Release pages also provide archives for Windows x64, Linux x64, macOS x64, and macOS ARM64. Each archive includes the Apache-2.0 license and third-party notices.

The URLs use the final repository name, storious/agulater.

Try the current source

Contributors working from this checkout need Bun 1.4+:

bun install --frozen-lockfile --ignore-scripts
bun tools/agulater.ts --help
bun test

This is a source-development path, not the normal installation path.

The npm package remains an optional compatibility distribution for users who already use Bun:

bun add --global --trust agulater

Use agulater@next only for an explicitly published prerelease.

Common tasks

Install or update a managed Agul runtime:

agulater runtime install --channel next
agulater runtime status
agulater runtime update --channel next

The normal runtime install also makes agul discoverable through PATH. Custom --prefix installs leave PATH alone unless --modify-path is supplied. To remove every managed Agul version and undo a PATH entry that Agulater added:

agulater runtime uninstall

Find and install one extension:

agulater catalog search web-search
agulater add agentkube:web-search --path . --type plugin
agulater prepare --path .

Update installed user extensions:

agulater update --all --user

Remove all plugins installed by Agulater while preserving manually declared plugins and the rest of the .agents package:

agulater remove --all --type plugin --user

Agulater keeps the runtime, extensions, and source .agents package separate:

• runtime manages Agul binaries and launchers.
• catalog, add, and update manage extension sources.
• prepare validates and compiles a package into runtime state.
• It never starts a model session on Agul's behalf.

Candidate artifacts

Maintainers build the standalone executable used by normal users with:

bun run build:standalone

They can also inspect the optional npm package without publishing it:

bun pm pack --dry-run --ignore-scripts
bun pm pack --destination ./dist --ignore-scripts

Install the resulting tgz only when testing the npm compatibility path:

bun add --global --trust ./dist/agulater-<version>.tgz

Neither Bun nor this package test is required after installing a standalone Agulater release.

Documentation

• Packages and preparation
• Catalogs and extensions
• Agul runtime lifecycle
• Schemas
• Changelog
• Contributing

Apache-2.0. See LICENSE and THIRD_PARTY_NOTICES.