Install once.Stay in sync.

The HubBound CLI installs your organization's Kits and Artifacts into every AI tool on a machine with one command, and the HubBound Runtime keeps that machine in sync in the background.

Book a demo

How do I install HubBound on my machine?

HubBound installs from one download per operating system: the full bundle (CLI and Runtime), the CLI alone or the Runtime alone, for Windows, macOS and Linux. Every link points at the latest GitHub release, so the file you get is always the current version.

Choose what to install

The full bundle is the recommended setup for a developer machine.

Choose your operating system

The download and the command change together.

Full bundle · Windows

Windows 10/11 · AMD64 · EXE · HubBound-Setup-amd64.exe

Download EXE

Or install it from a terminal

PS> Invoke-WebRequest https://github.com/hubbound/hubbound/releases/latest/download/HubBound-Setup-amd64.exe -OutFile HubBound-Setup-amd64.exe; Start-Process .\HubBound-Setup-amd64.exe

The Windows installer is not Authenticode-signed yet, so SmartScreen may warn before it runs. Compare its SHA-256 with the published list before you approve it.

Other formats:ZIP · AMD64SHA-256 for this file

Check that it works

  1. The CLI answers with its version
  2. The Runtime is running (checked through the CLI)
  3. Sign in to your organization

Straight from the release

What is the difference between the HubBound CLI and the Runtime?

The HubBound CLI is the command you run to sign in, install, sync and manage Kits and Artifacts; the HubBound Runtime is the background service that keeps working without you, installing mandatory distributions and reporting agent telemetry for Metrics. The full bundle installs both.

  • HubBound CLI

    hubbound

    A command-line tool with an interactive terminal screen, for the person at the keyboard. It acts only when you run it.

    • Signs you in with a device code (hubbound auth login)
    • Installs a Kit or an Artifact into every supported AI tool
    • Syncs, upgrades, lists and uninstalls what the machine has
    • Pins a project's tooling in hubbound.json and swaps global setups with profiles
    • Diagnoses and repairs tool integrations (hubbound doctor)

  • HubBound Runtime

    hubboundd

    A system service with a user agent and an update helper. It starts with the machine and works on a schedule.

    • Syncs your distributions and installs every mandatory Kit or Artifact; optional ones wait for you
    • Receives telemetry from your AI tools on the machine, then uploads it for HubBound Metrics
    • Keeps each tool's HubBound configuration in place and repairs it when it drifts
    • Checks for signed updates; applying one asks for approval again

Which one does a machine need?

  • A developer machine: the full bundle

    Commands when you want them, sync and telemetry when you don't. This is the recommended setup.

  • Hands-on or scripted installs: the CLI

    Install from hubbound.json or by name, with --no-tui for plain output. Nothing runs in the background.

  • Mandatory Kits with no manual step: the Runtime

    Distributions marked Mandatory arrive without anyone running a command. Signing in and health checks use the CLI.

    How distribution rules work

How does the HubBound CLI install a Kit or an Artifact?

The HubBound CLI installs a Kit or an Artifact with one command, hubbound install, which downloads the published version and writes it into every supported AI tool on the machine: Claude Code, Cursor, Codex CLI, GitHub Copilot and Antigravity. Flags narrow the tools, the scope or the profile.

One install command, part by part

hubbound install kit jane-a1b2c3/ai-tools-bundle@1.2.0 --scope local --tool claudecode,cursor

  1. The command

    hubbound install

    Downloads the Kit or Artifact and wires its files into your AI tools, in one step.

  2. What to install

    kit

    kit for a bundle, artifact for one skill, rule, hook, subagent or MCP server.

  3. Owner tag and name

    jane-a1b2c3/ai-tools-bundle

    Every Kit and Artifact is addressed as owner-tag/name, the same tag the Marketplace shows.

  4. Version, optional

    @1.2.0

    Pins one exact version. Leave it out to get the latest.

  5. Where it goes

    --scope local

    local writes into this project and records the pin in hubbound.json; global writes into your user tool folders. Without the flag, local is used when a hubbound.json is found.

  6. Which tools

    --tool claudecode,cursor

    A comma-separated subset. Without the flag, the CLI installs into all five.

The five tools, with their --tool ids

  • Claude Codeclaudecode
  • Cursorcursor
  • Codex CLIcodexcli
  • GitHub Copilotcopilot
  • Antigravityantigravity

Add --profile work to pin the install into a named global profile instead; it installs right away when that profile is active.

How do the HubBound file and profiles keep setups consistent?

The HubBound file (hubbound.json) pins the Kits and Artifacts a project needs, at exact versions or latest, so anyone who clones the repository runs hubbound install once and gets the same tooling. Profiles do the same for global setups: named sets, such as work and personal, that the CLI swaps without touching enforced or non-HubBound files.

hubbound.json
Illustrative sample
{"name": "my-app","artifacts": {"jane-a1b2c3/my-hook": "1.2.0"},"kits": {"jane-a1b2c3/ai-tools-bundle": "latest"}}

The file's structure is the one hubbound init creates. Names and versions are the CLI documentation's examples.

  • Create it once

    hubbound init writes hubbound.json in the current folder, named after the folder. It has two maps of pins: artifacts and kits.

  • Commit it, install from it

    A bare hubbound install reads the nearest hubbound.json and installs every pin, the way npm install reads package.json. Local installs and upgrades write the resolved version back.

  • Swap global setups with profiles

    Switching removes only the optional installs the previous profile owned, then applies the new one. Enforced installs and files without a HubBound marker are never touched.

How do I see and fix what is installed on a machine?

The HubBound CLI shows everything installed on a machine with hubbound manage, an interactive terminal screen that lists each Kit and Artifact per AI tool with its status and whether an admin or a team enforces it. hubbound sync, upgrade, uninstall and doctor then bring the machine back in line.

The screen's labels are the real ones; the Artifacts listed are an illustrative sample.

  • Pull your distributions

    Fetches every distribution you can see and materializes its files in your tools.

  • Move to the latest

    Upgrades every installed Kit and Artifact, and refreshes the pins in hubbound.json.

  • Remove it here

    Cleans the machine only. Add --remote to also retract your own distribution.

  • Fix a broken integration

    Rewrites the HubBound-owned configuration a tool is missing. hubbound doctor only diagnoses.

Which commands does the HubBound CLI include?

The HubBound CLI groups its commands into seven areas: distributions, profiles, account and device, the Runtime daemon, analytics, updates and troubleshooting. Running hubbound with no arguments opens an interactive terminal screen, and most commands also offer plain or JSON output for scripts.

Distributions

hubbound manage
Browse and manage everything installed.
hubbound sync
Pull distributions and materialize their files.
hubbound init
Create a hubbound.json in this folder.
hubbound install
Install a Kit or an Artifact, or every pin in hubbound.json.
hubbound upgrade
Upgrade one Kit or Artifact, or all of them.
hubbound uninstall
Remove a Kit or an Artifact from this machine.
hubbound retract
Remove your direct remote distribution.
hubbound list
List local installs, offline and without login.

Profiles

hubbound profile create
Create a named global profile.
hubbound profile switch
Switch the active global profile.
hubbound profile list
List profiles and the active one.

Account and device

hubbound auth login
Sign in with a device code.
hubbound auth status
Show who is signed in.
hubbound auth logout
Sign out and revoke this device.
hubbound device status
Show this device's analytics credential.

Runtime daemon

hubbound daemon status
Show the service status.
hubbound daemon health
Check that the daemon answers.
sudo hubbound daemon start
Also install, stop, restart and uninstall, as administrator.

Analytics

hubbound analytics doctor
Inspect the upload backlog, read-only.
hubbound analytics push
Force one upload cycle now.

Updates

hubbound update
Check for a signed update and apply it.
hubbound update check
Download and verify the latest update.
hubbound update apply --force
Apply the staged update, with approval.

Troubleshooting

hubbound doctor
Diagnose tool integrations without changes.
hubbound doctor repair
Repair missing HubBound-owned files.
hubbound version
Print the installed version.
hubbound docs
Open the CLI documentation.
Every flag and option is in the CLI documentation (opens in a new tab)

See how it all connects.

Each piece of HubBound builds on the others. Pick where you want to go next.

Artifacts & Kits

The standards you build, package and distribute.

Explore

Home

The big picture: what HubBound is and how it works.

Explore

Metrics

The visibility you get on AI usage, spend and delivery.

Explore

Security

On-demand Skill audits, with a verdict and a fix for every finding.

Explore

Org & Teams

How your organization and teams are structured.

Explore

Live Planning

Your agent's plan, shared, edited live and reviewed before it runs.

Explore

Memories, Projects and Ink

One bundle: your team's shared context, and Ink to ask it anything.

Explore

Put your team's tooling on every machine.

See the HubBound CLI and Runtime install a Kit end to end, then keep every machine on your organization's standard.

Book a demo