bridgeagent 0.16.5

The self-improving AI agent — creates skills from experience, improves them during use, and runs anywhere

BridgeAgent ☤

BridgeAgent is a BridgeMind fork of Nous Research's hermes-agent (MIT). It still uses Nous Research's inference backend by default. Branding, package name, CLI commands (bridge / bridgeagent / bridge-acp), env vars (BRIDGE_*), and the config dir (~/.bridgeagent/) have been rebranded; model identifiers and backend endpoints are unchanged.

The self-improving AI agent built by BridgeMind. It's the only agent with a built-in learning loop — it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions. Run it on a $5 VPS, a GPU cluster, or serverless infrastructure that costs nearly nothing when idle. It's not tied to your laptop — talk to it from Telegram while it works on a cloud VM.

Use any model you want — Nous Portal, OpenRouter (200+ models), NovitaAI (AI-native cloud for Model API, Agent Sandbox, and GPU Cloud), NVIDIA NIM (Nemotron), Xiaomi MiMo, z.ai/GLM, Kimi/Moonshot, MiniMax, Hugging Face, OpenAI, or your own endpoint. Switch with bridge model — no code changes, no lock-in.

A real terminal interface	Full TUI with multiline editing, slash-command autocomplete, conversation history, interrupt-and-redirect, and streaming tool output.
Lives where you do	Telegram, Discord, Slack, WhatsApp, Signal, and CLI — all from a single gateway process. Voice memo transcription, cross-platform conversation continuity.
A closed learning loop	Agent-curated memory with periodic nudges. Autonomous skill creation after complex tasks. Skills self-improve during use. FTS5 session search with LLM summarization for cross-session recall. Honcho dialectic user modeling. Compatible with the agentskills.io open standard.
Scheduled automations	Built-in cron scheduler with delivery to any platform. Daily reports, nightly backups, weekly audits — all in natural language, running unattended.
Delegates and parallelizes	Spawn isolated subagents for parallel workstreams. Write Python scripts that call tools via RPC, collapsing multi-step pipelines into zero-context-cost turns.
Runs anywhere, not just your laptop	Six terminal backends — local, Docker, SSH, Singularity, Modal, and Daytona. Daytona and Modal offer serverless persistence — your agent's environment hibernates when idle and wakes on demand, costing nearly nothing between sessions. Run it on a $5 VPS or a GPU cluster.
Research-ready	Batch trajectory generation, trajectory compression for training the next generation of tool-calling models.

---

Quick Install

Linux, macOS, WSL2, Termux

curl -fsSL https://bridgeagent.ai/install.sh | bash

Windows (native, PowerShell)

Heads up: Native Windows runs BridgeAgent without WSL — CLI, gateway, TUI, and tools all work natively. If you'd rather use WSL2, the Linux/macOS one-liner above works there too. Found a bug? Please file issues.

Run this in PowerShell:

iex (irm https://bridgeagent.ai/install.ps1)

The installer handles everything: uv, Python 3.11, Node.js, ripgrep, ffmpeg, and a portable Git Bash (MinGit, unpacked to %LOCALAPPDATA%\bridgeagent\git — no admin required, completely isolated from any system Git install). BridgeAgent uses this bundled Git Bash to run shell commands.

If you already have Git installed, the installer detects it and uses that instead. Otherwise a ~45MB MinGit download is all you need — it won't touch or interfere with any system Git.

Android / Termux: The tested manual path is documented in the Termux guide. On Termux, BridgeAgent installs a curated .[termux] extra because the full .[all] extra currently pulls Android-incompatible voice dependencies.

Windows: Native Windows is fully supported — the PowerShell one-liner above installs everything. If you'd rather use WSL2, the Linux command works there too. Native Windows install lives under %LOCALAPPDATA%\bridgeagent; WSL2 installs under ~/.bridgeagent as on Linux. The only BridgeAgent feature that currently needs WSL2 specifically is the browser-based dashboard chat pane (it uses a POSIX PTY — classic CLI and gateway both run natively).

After installation:

source ~/.bashrc    # reload shell (or: source ~/.zshrc)
bridge              # start chatting!

---

Getting Started

bridge              # Interactive CLI — start a conversation
bridge model        # Choose your LLM provider and model
bridge tools        # Configure which tools are enabled
bridge config set   # Set individual config values
bridge gateway      # Start the messaging gateway (Telegram, Discord, etc.)
bridge setup        # Run the full setup wizard (configures everything at once)
bridge claw migrate # Migrate from OpenClaw (if coming from OpenClaw)
bridge update       # Update to the latest version
bridge doctor       # Diagnose any issues

📖 Full documentation →

---

Skip the API-key collection — Nous Portal

BridgeAgent works with whatever provider you want — that's not changing. But if you'd rather not collect five separate API keys for the model, web search, image generation, TTS, and a cloud browser, Nous Portal covers all of them under one subscription:

• 300+ models — pick any of them with /model <name>
• Tool Gateway — web search (Firecrawl), image generation (FAL), text-to-speech (OpenAI), cloud browser (Browser Use), all routed through your sub. No extra accounts.

One command from a fresh install:

bridge setup --portal

That logs you in via OAuth, sets Nous as your provider, and turns on the Tool Gateway. Check what's wired up any time with bridge portal info. Full details on the Tool Gateway docs page.

You can still bring your own keys per-tool whenever you want — the gateway is per-backend, not all-or-nothing.

---

CLI vs Messaging Quick Reference

BridgeAgent has two entry points: start the terminal UI with bridge, or run the gateway and talk to it from Telegram, Discord, Slack, WhatsApp, Signal, or Email. Once you're in a conversation, many slash commands are shared across both interfaces.

Action	CLI	Messaging platforms
Start chatting	bridge	Run bridge gateway setup + bridge gateway start, then send the bot a message
Start fresh conversation	/new or /reset	/new or /reset
Change model	/model [provider:model]	/model [provider:model]
Set a personality	/personality [name]	/personality [name]
Retry or undo the last turn	/retry, /undo	/retry, /undo
Compress context / check usage	/compress, /usage, /insights [--days N]	/compress, /usage, /insights [days]
Browse skills	/skills or /<skill-name>	/<skill-name>
Interrupt current work	Ctrl+C or send a new message	/stop or send a new message
Platform-specific status	/platforms	/status, /sethome

For the full command lists, see the CLI guide and the Messaging Gateway guide.

---

Documentation

All documentation lives at bridgeagent.ai/docs:

Section	What's Covered
Quickstart	Install → setup → first conversation in 2 minutes
CLI Usage	Commands, keybindings, personalities, sessions
Configuration	Config file, providers, models, all options
Messaging Gateway	Telegram, Discord, Slack, WhatsApp, Signal, Home Assistant
Security	Command approval, DM pairing, container isolation
Tools & Toolsets	40+ tools, toolset system, terminal backends
Skills System	Procedural memory, Skills Hub, creating skills
Memory	Persistent memory, user profiles, best practices
MCP Integration	Connect any MCP server for extended capabilities
Cron Scheduling	Scheduled tasks with platform delivery
Context Files	Project context that shapes every conversation
Architecture	Project structure, agent loop, key classes
Contributing	Development setup, PR process, code style
CLI Reference	All commands and flags
Environment Variables	Complete env var reference

---

Migrating from OpenClaw

If you're coming from OpenClaw, BridgeAgent can automatically import your settings, memories, skills, and API keys.

During first-time setup: The setup wizard (bridge setup) automatically detects ~/.openclaw and offers to migrate before configuration begins.

Anytime after install:

bridge claw migrate              # Interactive migration (full preset)
bridge claw migrate --dry-run    # Preview what would be migrated
bridge claw migrate --preset user-data   # Migrate without secrets
bridge claw migrate --overwrite  # Overwrite existing conflicts

What gets imported:

• SOUL.md — persona file
• Memories — MEMORY.md and USER.md entries
• Skills — user-created skills → ~/.bridgeagent/skills/openclaw-imports/
• Command allowlist — approval patterns
• Messaging settings — platform configs, allowed users, working directory
• API keys — allowlisted secrets (Telegram, OpenRouter, OpenAI, Anthropic, ElevenLabs)
• TTS assets — workspace audio files
• Workspace instructions — AGENTS.md (with --workspace-target)

See bridge claw migrate --help for all options, or use the openclaw-migration skill for an interactive agent-guided migration with dry-run previews.

---

Contributing

We welcome contributions! See the Contributing Guide for development setup, code style, and PR process.

Quick start for contributors — clone and go with the compatibility setup helper:

git clone https://github.com/BridgeMind/BridgeAgent.git bridgeagent
cd bridgeagent
./setup-bridge.sh     # installs uv, creates venv, installs .[all], sets up the local CLI
bridge                # uses the installed BridgeAgent CLI

Manual path (equivalent to the above):

curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv .venv --python 3.11
source .venv/bin/activate
uv pip install -e ".[all,dev]"
scripts/run_tests.sh

---

Community

• 💬 Community
• 📚 Skills Hub
• 🐛 Issues
• 🔌 computer-use-linux — Linux desktop-control MCP server for BridgeAgent and other MCP hosts, with AT-SPI accessibility trees, Wayland/X11 input, screenshots, and compositor window targeting.
• 🔌 BridgeClaw — Community WeChat bridge: Run BridgeAgent and OpenClaw on the same WeChat account.

---

License

MIT — see LICENSE.

Built by BridgeMind.