BootAgent

One place to install, configure, and keep your AI coding Agents ready.

简体中文

BootAgent is a local desktop workspace for AI coding Agents. It turns a fresh machine into a usable, repeatable setup without asking you to edit several tool-specific config files by hand.

What it does

• Detects, installs, updates, and launches supported CLI and desktop Agents.
• Connects Agents to built-in or custom Providers, with model selection and protocol-aware connection checks.
• Saves reusable Profiles and applies the right configuration to each Agent.
• Bootstraps required runtimes such as Node.js, uv, and Aider's managed Python when needed.
• Keeps long-running installs visible and cancellable in the Task Center.
• Imports and exports Providers, Profiles, and selected MCP servers. API keys and MCP secrets are excluded by default; password-encrypted or explicitly confirmed plaintext export is also available.
• Discovers MCP servers from initialized Claude Code, Codex, OpenCode, Kilo CLI, and Hermes installations, and applies selected servers across them from the MCP Registry. Scanning runs in the background; edits are explicit and local.
• Creates backups, writes atomically, and keeps credentials in private local storage. The latest three historical versions are kept per Profile, Provider, MCP, Agent configuration target, and Skill; backups live under ~/.bootagent/backup and the per-target count can be changed in Settings.
• Checks for BootAgent updates and installs release artifacts through the built-in updater.

Supported Agents

PPIO and Novita are built in. Any OpenAI-compatible or Anthropic-compatible Provider can be added from the Provider page. BootAgent probes the protocol an Agent actually uses; an endpoint that only exposes a different API is rejected before configuration is written.

The MCP Registry is user-level only and stored locally. It supports stdio, HTTP, and SSE servers for Claude Code, Codex, OpenCode, Kilo CLI, and Hermes. Select sync targets explicitly and apply changes when ready; clearing all targets removes the server from Agent configs but keeps it in the Registry. Deleting a server removes it from Agent configs first and from the Registry only after the application succeeds. MCP exports are selected per server and carry no Agent bindings, so they can be imported on another machine before choosing local targets.

Download

Download the latest macOS, Windows, or Linux package from GitHub Releases. Linux releases provide deb, rpm, AppImage, and OTA zip packages for amd64 and arm64. Release artifacts include SHA-256 checksums. The current channel is technical-preview-unsigned while Wails remains in Alpha; platform signing and notarization are not yet provided.

BootAgent does not redistribute Agent packages and does not bundle Node.js, Git, WebView, or API keys. Missing prerequisites are reported with a link to the official installation instructions.

Build from source

Requirements: Go, Node.js, pnpm 11.21.0, and the target platform's WebView dependencies. Linux builds use GTK4 and WebKitGTK 6.0; GTK3 is not supported.

git clone https://github.com/MaimoryLab/BootAgent.git
cd BootAgent
cd frontend && pnpm install --frozen-lockfile && pnpm run build && cd ..
go run -tags wails ./cmd/bootagent-desktop

For the usual development loop, install Task and run task dev. Useful checks:

go test ./...
go test -race ./...
go vet ./...
cd frontend && pnpm run test && pnpm run build

Project links

• AI Agent Kit: set up an Agent environment step by step
• Documentation: specifications and architecture decisions
• Public site repository
• Issues and feature requests

Star History

Sponsors

BootAgent is released under the Apache License 2.0. Third-party notices are listed in NOTICE.