Boost — faster agents, faster CI

_{For coding agents, their commands, and the CI that runs them.}

_{Sponsored by JFrog}

---

Humans and coding agents spend too much time waiting for commands to finish and sifting through noisy output. Boost is a single binary that drops into three places at once:

• your terminal — prefix any command with boost
• your coding agent — boost init wires up Cursor, Claude Code, Codex, Gemini CLI, and more
• your CI — one line: uses: jfrog/boost@v0

Same binary, same acceleration, same telemetry — wherever your builds run.

Quick Start

CLI — prefix any command with boost

Install:

curl -fsSL https://raw.githubusercontent.com/jfrog/boost/main/install.sh | bash

Use:

boost docker build -t myapp .
boost npm ci
boost pytest

Coding agent — auto-wire Cursor, Claude Code, Codex, and more

Run the interactive setup in any project:

boost init

It detects your installed editors and CI providers and registers hooks so every tool call the agent makes gets wrapped by boost. Re-run it any time your editor / agent list changes.

CI — one line in your workflow

steps:
  - uses: jfrog/boost@v0
  - uses: actions/checkout@v4
  ...

The action pins to the rolling v0 major; see releases for the latest tag.

Why Boost

• One binary, three surfaces — CLI, coding agent, and CI all share the same runtime and behave identically.
• 60–90% fewer log tokens — strips noise from command output before it reaches your agent's context window.
• Deep OTel context — every wrapped command emits OpenTelemetry traces and metrics your agents can reason about.

Before / after

Same npm ci, same result. What changes:

• ~15× fewer tokens in your agent's context — 9.8k → 640 on a typical install.
• Faster reruns via content-addressed cache — seconds instead of minutes.
• Deep OTel trace of every command — timing, cache hits, exit code — routable to your backend.

# Without boost — ~9,800 tokens of log noise in your agent's context
$ npm ci
npm warn deprecated inflight@1.0.6 / rimraf@3.0.2 / glob@7.2.3 …
added 1285 packages, audited 1286 in 45s
found 0 vulnerabilities

# With boost — ~640 tokens, same result, cache-backed
$ boost npm ci
[OK] npm ci · 1,285 packages restored from boost cache in 2.4s · 0 vulnerabilities

Supported tools

Coding agents: Cursor · Claude Code · GitHub Copilot · Codex CLI · Gemini CLI · OpenCode · Windsurf · Cline

CI platforms: GitHub Actions · GitLab CI (coming soon) · Jenkins (coming soon) · CircleCI (coming soon) · Azure Pipelines (coming soon)

Usage examples

Prefix any command with boost — anywhere you'd normally run it.

• boost docker build ... — compressed build log, layer-cache summary, Docker metrics in OTel
• boost npm ci — dependency summary, local package cache, retry-safe output
• boost pytest — per-test pass/fail/duration stored locally, quiet output on green runs
• boost gh run view --log — CI log stream condensed to top failures plus summary

Update

boost update

Documentation

See the full documentation for commands, configuration, OpenTelemetry export, and CI recipes.

Security & Privacy

• Local-first. Command history and raw OTel traces stay on your machine.
• Only metadata leaves. Exported spans carry timing, exit code, and cache stats — never raw logs, file contents, or env values. Secrets matching patterns like *_TOKEN, *_SECRET, AWS_*, DATABASE_URL are redacted before write or export.
• Open protocol, signed binaries. OpenTelemetry-native; point BOOST_OTEL_ENDPOINT at your own backend. Binaries ship signed via GitHub Releases.

Full policy, supported versions, and how to report a vulnerability: see SECURITY.md.

License

Copyright © 2026 JFrog Ltd. All rights reserved. See LICENSE and TERMS_OF_USE.md.

---

Dedicated to the memory of Dima Gershovich — a brilliant engineer, a talented musician, and a dear friend. Read Dima's story