BootAgent

Many Agents. One place to manage them.

简体中文

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. The terminal used to launch CLI Agents can be chosen in Settings; the platform's built-in terminal remains the default.
• Migrates existing Codex and ChatGPT Desktop conversations into BootAgent's bootagent provider bucket from their Agent rows. This operation intentionally creates no history backup.
• Connects Agents to built-in or custom Providers, with model selection and protocol-aware connection checks.
• Saves reusable Profiles. An Agent's own configuration screen is where you pick the Profile it uses, and where its model can be changed directly.
• Carries a Profile's reasoning effort (off, low, medium, high, max) into every Agent whose own config format documents a place for it, translating the scale to what each one accepts. Agents with no documented depth setting are left alone rather than given invented keys.
• 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.
• Provides local API format conversion and an optional launch-at-login setting; both are off by default, and enabling conversion offers to enable launch at login.
• 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. When the domestic mirror setting is enabled, update checks and downloads use the Gitee mirror; otherwise they use GitHub.

Supported Agents

DSH Desktop heads the desktop list. It is published by anywhere-labs rather than by DeepSeek, so the download row labels it a third-party application; the DeepSeek mark beside it identifies the model it drives, not its publisher.

Claude Desktop is detected and launched on macOS and Windows, but its installation remains manual. After writing the configuration, BootAgent directs the user to the official download page. BootAgent writes and selects a BootAgent-owned 3P profile for direct Anthropic-compatible endpoints; it does not download Claude Desktop, proxy requests, or provide a restore-to-1P action. The selected model ID must contain claude (case-insensitive).

JieKou.AI, PPIO, Novita, DeepSeek and Moonshot are built in, listed in that order. 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.

DeepSeek Harness can also be activated against DeepSeek's own official route, which its shipped configuration already defines, instead of going through a generic OpenAI-compatible endpoint.

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. macOS artifacts are signed with Developer ID and notarized; the release channel remains technical-preview-unsigned while Wails is in Alpha.

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.