Aigent Hive

A provider-neutral local harness for Codex, Claude Code, and Gemini Antigravity.

English · 한국어

Hive gives subscription-authenticated agent hosts one consistent setup, Skill routing, project knowledge, durable role/run state, usage safeguards, and safe update contracts. It never asks for model-provider API keys, calls model-provider APIs, or replaces the host's own model runtime.

Stable 0.14.0 is the current public release.

Install the current stable release

0.14.0 is published on npm as latest, with a normal GitHub Release and annotated Git tag.

npm install -g aigent-hive

Or pin the exact version:

npm install -g [email protected]

The npm installer requires Node.js and npm. The installed hive runtime is a native Rust binary and does not require Node.js.

Expected stable version label:

AIgent Hive v0.14.0 (released 2026-10-30)

macOS and Linux with curl

curl --proto '=https' --tlsv1.2 -LsSf \
  https://unpkg.com/[email protected]/install.sh | sh

Windows PowerShell 5.1+

irm https://unpkg.com/[email protected]/install.ps1 | iex

Windows Command Prompt

curl.exe -fLo install-aigent-hive.cmd https://unpkg.com/[email protected]/install.cmd && install-aigent-hive.cmd

The direct installers fetch the same native package bytes from npm, verify the embedded exact-version SHA-256, and record direct-install ownership. They do not require npm, Node.js, or PowerShell 7.

Optional one-prompt setup

If you want Codex, Claude Code, or Gemini Antigravity to guide the entire user-level installation, paste the following prompt instead of following the manual steps below.

I want the optional one-prompt Aigent Hive setup. Work only at user scope; do not inspect,
initialize, or change any project, repository, folder, or current working directory.

Install the current stable release 0.14.0. The stable install guidance is
https://github.com/gvm1229/aigent-hive#install-the-current-stable-release.
Detect my operating system and active host (Codex, Claude Code, or Gemini Antigravity), asking
me if either is unclear. Check whether Node.js and npm are available. If they are missing,
give me the official OS-specific Node.js installation command and request any approval the host
requires before installing it. Then install the exact Hive release I selected using the official
method in the linked guidance, verify `hive --version`, then run `hive update` once and select
the active host when prompted.

Then begin interactive global setup in this conversation. For a first setup, ask only whether I
want English or Korean first; continue one question at a time. For existing settings, first ask
whether I want to change one setting or review everything. Do not start project setup afterward:
offer the separate project-setup prompt instead. Never ask for provider API credentials or install
an optional third-party Skill.

This option installs only the current stable release.

What changed in 0.14.0

• Answer local CLI questions to configure user and project settings in English or Korean. Setup does not call a model.
• Reuse saved choices, change one setting, or resume interrupted setup. User notes and role assignments remain preserved.
• New installations start with automatic usage stops disabled. Existing protection choices require review before changes.
• Preview removal with hive uninstall --dry-run. Confirm the program removal while keeping settings, knowledge, history and project data for reinstallation.
• When protection is enabled, choose a remaining-usage floor from 0 through 99%. Reset detection, exhausted-quota protection and midway monitoring remain separate controls. A 0% floor does not disable exhausted-quota protection or guarantee zero credit charges.
• Updates from 0.13.1 continue into local setup questions. Without an interactive terminal, the approved preserving update keeps existing choices, leaves new optional features off and reports pending questions. Historical update inputs still require complete ownership verification.
• Downloads, hooks, external notifications and Windows Codex midway interruption still require their own consent. Monitoring checks the required app communication capabilities. Other operating systems and remote or cloud tasks lack direct interruption support; app survival and direct user resume remain required.
• Existing answer files remain supported. New records distinguish explicit choices, defaults, inherited settings and unknown historical origins.

Earlier changes in 0.13.1

• With midway monitoring enabled, existing guarded chats stop at the configured remaining-usage floor. AI children inherit their owning chat's policy. Codex stays open, and a direct resume or new message does not repeat the same floor stop. Independent zero-quota checks remain.
• A failed persistent reading retries through a fresh native process. Both paths use the same provider. Keep 15-second start intervals, a five-second timeout per path and one stop after 60 continuous seconds without a valid reading.
• Reset comparison ignores expired readings and a prior process baseline. A fresh reading establishes the next baseline after a restart. Long chats keep their usage-control connection.
• Updates preserve knowledge, settings, incident history and the monitoring choice. Selected-Skill profiles and Windows path variants update correctly. Repeated updates reuse an identical staged executable.
• The close-only notice shows the official logo, remaining usage, the applied floor and actual stop confirmation. Resume directly in Codex. Ask Codex to disable midway monitoring; no PowerShell entry or unlock procedure is required.
• Direct interruption supports Windows 11 x64 with Codex 26.1013.4894.0 or 26.1016.6573.0. Already-started ordinary external commands may continue; separate local AI sessions and subagents remain interruption targets. Other operating systems, remote tasks and cloud tasks lack direct interruption support.
• Monitoring requires explicit opt-in after hive usage monitor preview; installation does not enable a new monitor. Saved choices remain. Detection can consume some new quota and does not guarantee simultaneous server processing or billing termination.

Earlier improvements remain in the 0.13.0 release notes and 0.12.0 release notes.

Supported targets

| Platform | Native target | 0.14.0 evidence | | --- | --- | --- | | macOS Apple Silicon | aarch64-apple-darwin | Public numbered-test acceptance | | macOS Intel | x86_64-apple-darwin | Candidate runtime qualified | | Linux x86_64 | x86_64-unknown-linux-musl | Public numbered-test acceptance | | Linux arm64 | aarch64-unknown-linux-musl | Native candidate qualification | | Windows x86_64 | x86_64-pc-windows-msvc | Public numbered-test acceptance |

The accepted public test covers setup, cancellation, recovery, updates, removal and reinstallation on Windows x64, Linux x64 and macOS arm64. Windows also covers actual Codex CLI registration and an idle monitor. This does not prove live desktop-model or quota sensing on every host. Claude Code subscription-backed sessions remain unverified. Stable 0.14.0 uses explicit macOS ad-hoc signing and publishes Windows as unsigned unless free SignPath Foundation signing is approved. See the code signing policy for the exact trust boundary.

First setup

First install the executable, then run one global update command. Project setup remains a separate, explicit action for each project.

1. Install the Hive CLI

Use one command from Install the current stable release above. The npm installation provides the hive command only. It does not create user settings, host projections, or a project harness.

2. Initialize or update the global Hive installation

In an interactive terminal, run:

hive update

For a first npm installation, choose one or more hosts when prompted. Hive installs only its owned minimum user projection. For an existing installation, it refreshes and validates only the authenticated saved hosts; it does not inspect or change projects.

3. Answer any new global question

Continue the local questions shown by hive update. Review the proposed changes before applying them. Choices such as semantic search can affect storage, downloads and future behavior. Cancelling does not supply consent. A preserving update without an interactive terminal keeps existing choices and reports any questions that still need an answer.

After confirmation, Hive applies and validates its global user files. Project setup remains separate.

4. Configure one project

Open the exact project in the host and paste this separate prompt:

Configure the local Aigent Hive harness for this project. Use my existing global Hive preferences, inspect only this project, show the exact write preview, and ask me only about choices that require my approval.

Use this prompt once for each repository. It inherits your global preferences and only changes the named project after showing its exact write preview. If the host is not open in the project, name the project with an absolute path instead:

Configure the local Aigent Hive harness for the project at /absolute/path/to/project. Use my existing global Hive preferences, inspect only that project, show the exact write preview, and ask me only about choices that require my approval.

Do not use the project prompt from your home directory without a project path. A request that includes both scopes completes global setup first and asks before inspecting or changing a project.

Neither prompt authorizes an update, optional third-party Skill, or provider-credential access.

Hive previews its exact owned write set, preserves foreign guidance bytes, and keeps canonical knowledge in Markdown.

Updating

hive update

This performs an immediate version check and reconciles Hive-owned global user files even when the executable is already current. If a newer version exists, Hive explains the exact update and asks before invoking the authenticated install owner. Without explicit update confirmation, declining, closing stdin or running non-interactively causes no installation. The first initialization requires an interactive host selection.

When daily checks are enabled, a successful check is throttled for 24 hours. An offline or failed check is not recorded as successful, so the next Codex, Claude Code, or Antigravity session retries it.

Hive never installs an update silently.

Move global knowledge to another computer

Use a .hivekb bundle to move global knowledge between computers. --user-root is the user home directory, not its .hive subdirectory. Use the command block for the shell that is running it; do not copy a Windows environment variable into a macOS or Linux shell, or the reverse.

The bundle contains portable canonical knowledge. It does not copy SQLite indexes, runtime state, project-private knowledge, credentials, or absolute local paths.

macOS and Linux shell

Export the global bundle:

bundle="$HOME/Downloads/aigent-hive-knowledge-YYYY-MM-DD.hivekb"
hive knowledge export --user-root "$HOME" --scope global --bundle "$bundle" --output json
shasum -a 256 "$bundle"

On the destination computer, replace the bundle path and expected checksum with the values you received. Run the dry run first. Run --apply only after the file exists, the checksum matches, and the dry run reports no conflict or validation error.

bundle="$HOME/Downloads/aigent-hive-knowledge-YYYY-MM-DD.hivekb"
shasum -a 256 "$bundle"
hive knowledge import --user-root "$HOME" --bundle "$bundle" --dry-run --output json
hive knowledge import --user-root "$HOME" --bundle "$bundle" --apply --output json
hive knowledge lint --target "$HOME" --user-root "$HOME" --output json

Windows PowerShell

Export the global bundle:

$bundle = "$env:USERPROFILE\Downloads\aigent-hive-knowledge-YYYY-MM-DD.hivekb"
hive knowledge export --user-root $env:USERPROFILE --scope global --bundle $bundle --output json
Get-FileHash -Algorithm SHA256 $bundle

On the destination computer, use the returned Hash value to verify the received bundle. Run --apply only after the file exists, the hash matches, and the dry run reports no conflict or validation error.

$bundle = "$env:USERPROFILE\Downloads\aigent-hive-knowledge-YYYY-MM-DD.hivekb"
Get-FileHash -Algorithm SHA256 $bundle
hive knowledge import --user-root $env:USERPROFILE --bundle $bundle --dry-run --output json
hive knowledge import --user-root $env:USERPROFILE --bundle $bundle --apply --output json
hive knowledge lint --target $env:USERPROFILE --user-root $env:USERPROFILE --output json

Automatic dispatch safeguard

When enabled, Hive checks subscription usage immediately before a new automatic dispatch:

hive usage enforce --target <project> --session-id <id> --process-id <pid> --output json
hive run resume --dispatch-intent automatic --target <project> --run <run-id> --capabilities <json> --output json

The first command is only a preflight; it never authorizes dispatch by itself. External runtime cancellation is auxiliary evidence and never replaces durable goal/task state. Ordinary quick-answers and manual work do not run this automatic-dispatch gate.

Load-tested for large knowledge bases

A chunk is a retrieval-sized piece of a Wiki page, not one complete document. To make the scale concrete, the qualification fixture splits 25 deliberately long Wiki pages into 2,000 chunks each: 50,000 search-ready pieces in total. Its portable-bundle scenario also carries a registry of 100 portable collections. This is a deliberately large test fixture, rather than a claim that an ordinary user has 50,000 documents.

| Qualification | Scenario | Latest p95 | Acceptance limit | | --- | --- | ---: | ---: | | Fresh local retrieval | 50,000 chunks | 170 ms | 500 ms | | Warm repeat retrieval | 50,000 chunks | 0.14 ms | 100 ms | | Portable bundle export | 100 collections, 50,000 chunks | 1.04 s | 5 s | | Bundle import and index rebuild | 100 collections, 50,000 chunks | 3.27 s | 15 s |

These release-build, local-SSD measurements are qualification evidence; real timing varies with hardware and the shape of the knowledge. See the qualification record for the method and limits.

What Hive owns

• Hive-owned marker blocks and manifest-listed files only
• Provider-neutral Skills and thin host projections
• Canonical Markdown/YAML/TOML state
• Disposable SQLite indexes rebuilt from canonical text
• Verified direct-install receipts

Hive does not own provider credentials, model sessions, foreign guidance, OMX/OMC state, Homebrew/WinGet installations, or optional third-party Skills without explicit approval.

Architecture and maintainer docs

• Documentation home
• Complete document index
• Product overview
• Development and verification
• Active plan
• Current project state
• Source layout
• Release and update trust boundary
• Code signing policy
• Product decisions

Development requires Rust stable, Python 3.13 for conformance tests, and PowerShell 7 for Windows development/release workflows. Consumer installations do not require Python or PowerShell 7.

python scripts/dev-check.py pre-push

License

Apache-2.0. See LICENSE.