brigade 中文翻譯降低自託管智能體系統的入門門檻

The original spinabot/brigade repository lists 0 stars. The Chinese translation, yangshun2005/brigade-cn, was published on 2026-10-23 and also has 0 stars. Neither number is impressive, and I'm not going to pretend otherwise. What makes the translation worth a look is not popularity — it's that brigade itself is a fairly dense piece of software, and the Chinese version adds a guided entry layer on top of a straight translation of the README.

Let me describe what the project claims to be, then what the translation actually changes for a Chinese-speaking developer.

What brigade is, per its own README

Brigade is a self-hosted personal AI agent system. The README frames it as "a team of AI agents running on a real org chart, sharing one long-term memory called Tideline." The practical consequences of that framing:

• Agents delegate tasks to each other.
• A model can be swapped mid-task without losing context.
• Whatever one agent learns is available to the others through the shared memory.
• Actions can be executed across "1,000+ apps" you already use.

The deployment story is deliberately small: the same crew is said to run on a Raspberry Pi or a server. Default storage is a small filesystem install; you can switch to a self-hosted Convex database if you need it. Models supported include Claude, GPT, Gemini, Llama, and local Ollama.

The access story is broader than a terminal. The README lists a chat TUI, plus WhatsApp, Telegram, Slack, Discord, iMessage, and BlueBubbles — and mentions watches, Meta smart glasses, and Meta Quest as entry points. I can't verify any of those integrations from the README text alone; I'm reporting what it states.

The privacy claims are specific enough to quote rather than paraphrase: no account creation, no SaaS in the middle, no telemetry, API keys stay on your machine. Privileged operations wait for your approval. Data lives under ~/.brigade/.

The install path

Two commands, macOS and Linux only per the README:

curl -fsSL https://brigade.spinabot.com/install.sh | sh
brigade

The script installs Node if needed and doesn't require sudo. After that you land in a chat TUI.

There's also an expose subcommand that puts your agent on the public internet. The README gives it a theatrical name — B³, "Brigade Bloody Benchmark" — and describes the mechanics plainly enough: HTTPS at the edge, no account, no config, Cloudflare by default, or bring your own relay from bore, frp, or sish (all open source). An invisible key travels with the request; unauthorized visitors get a 401. The boring alias is brigade expose, and brigade expose stop tears it down.

That's the whole quick-start. Everything past it — isolated agents with separate workspaces and credentials, persistent memory, a skills system, a cron scheduler, sub-agent fan-out, org hierarchy — the README gestures at but the excerpt I'm working from doesn't detail.

What the Chinese version adds

Two things, and they're worth separating.

First, a translation of the README body. The page states this explicitly: the lower section is a faithful Chinese rendering of the original documentation, and the original English README is kept alongside as README_en.md. So you can diff them.

Second, a section the translation calls 「中文快速上手」 — a supplementary guide that is not part of the original. The page is upfront about this being added content rather than translated content. It covers:

• What the project is and what problem it solves, in about a paragraph.
• The shortest path to running it: install script, brigade, then talk.
• brigade expose and brigade expose stop, with a warning that this publishes your agent to the internet.
• Environment requirements: OS, hardware, Node runtime, storage options, model access, network.
• A "common pitfalls" list.

That last list is the part I'd actually point people at. It flags four things:

1. You need model access. Either an API key, or a subscription login (Claude / ChatGPT / Copilot), or reuse an existing Claude Code / Codex CLI session. The README stresses the key never leaves your machine.
2. brigade expose is a real exposure. Default Cloudflare, optional self-hosted relay, invisible key, 401 for unauthorized access. The translation's phrasing is blunt: know that you're publishing a service before you run it.
3. All data is under ~/.brigade/. Relevant for backup and migration.
4. Storage mode is a choice. Filesystem by default; Convex requires extra deployment, and the translation notes the original doesn't spell out the steps or resource requirements.

On environment: the install command is marked macOS / Linux. Whether Windows works is not stated in the original, and the translation doesn't invent an answer. Node is required and the script installs it if missing; the exact engine version is declared in package.json but isn't visible in the material I have. Network-wise, the install script pulls from brigade.spinabot.com, and the translation notes that users in mainland China may hit slow downloads and may need their own acceleration method — the original provides no mirror.

I appreciate that last note. It's the kind of thing a translator notices because they've hit it, and it's exactly the sort of gap a literal translation leaves open.

Why a Chinese README matters here

For a project with a short quick-start, translation is a convenience. For brigade, the README is long and layered — CLI reference, in-chat commands, configuration and storage, the B³ section with its own vocabulary. A developer whose English reading is slow will bounce off that before they ever get to brigade in a terminal.

The supplementary guide shortens the distance between "found the repo" and "saw the TUI." That's the whole value proposition. It's not a new feature, not a fork, not a patch. It's an on-ramp.

There's a second, quieter benefit: the translated page keeps the English README in the repo as README_en.md. If a sentence reads oddly in Chinese, you can check the source without leaving GitHub. The page also invites issues and PRs for inaccuracies, which is the right posture for a translation of a project that's still moving — the original is at v1.9.0 per the B³ section, and docs will drift.

What I'd verify before committing

A few things the material doesn't settle, and which you should check against the live repo or by running it:

• Windows support. Unstated. If you're on Windows, assume nothing.
• Minimum hardware. The README says Raspberry Pi or a server; no specs given.
• Node version. Declared in package.json, not in the docs excerpt.
• Convex migration steps. Not documented in what I have.
• The 1,000+ app integrations and the wearable/VR entry points. Listed, not detailed.

None of these are red flags on their own. They're just the boundary of what the README tells you.

Where to look

• Chinese version: https://github.com/yangshun2005/brigade-cn
• Original: spinabot/brigade

If you read Chinese and want to evaluate brigade without parsing a long English README first, the translation is the faster door. If you read English comfortably, go straight to the original — the translation adds a guide, not information the source lacks. And if you find a mistranslation, the page says to file it. That's the maintenance model: readers patching a moving target.

Chinese documentation: https://github.com/yangshun2005/brigade-cn

I'm an independent enterprise AI delivery consultant — private LLM deployment, RAG, agent workflows, AIOps. If your team is stuck somewhere in that stack, my inbox is open.