原来多个 AI agent 组队干活，比单个通用 agent 高明在这：每个角色绑自己最擅长的模型，记忆和技能跨聊天累积。不是轮流调用，而是通过 handover 传一句简报就把任务交出去。本地跑，文件状态全在 ~/.crew44 里，免费 MIT。凌晨看这个实现路径，感觉团队协作的思路终于落到 agent 层面了。

getcrew44/crew44

Source: https://github.com/getcrew44/crew44

Crew44

A local-first orchestrator for running specialist AI agents on your own machine.

Download · Website · What’s new

Crew44 turns the AI agents you already run — Claude Code, Codex, Gemini, Cursor, and more — into a coordinated team. Instead of one generalist agent re-explaining context to itself all day, you assemble specialists, bind each to the model that wins at its job, and let them hand work off to each other inside one shared workspace.

Everything runs on your machine. State is plain files under ~/.crew44/. No cloud account, no subscription, no telemetry — the only network traffic is whatever your underlying coding agent already makes.

https://github.com/user-attachments/assets/ce6e5293-6c58-4c37-8e00-74d654d2277c

Download

Grab a signed desktop build for your platform — free, no account required:

→ crew44.io/download

Prefer to build it yourself? See Getting started.

Why Crew44

Supported runtimes

Crew44 detects and routes to any of these installed on your machine:

Claude Code · Codex · Cursor Agent · Gemini CLI · Hermes · Kimi · OpenCode · OpenClaw · Pi · Qoder · Qwen Code

The same skills folder runs across every provider, so you’re never locked in. Have another CLI? The runtime layer is a small Go interface — add an adapter under daemon/internal/backendagent/ and it shows up in the picker.

Core concepts

The default crew ships with a Partner, an Engineer, a Product Lead, and a Designer — each owning a role, a model, and its own skills folder.

How it works

┌─────────────────┐  WebSocket JSON-RPC   ┌──────────────────┐    spawn    ┌─────────────────┐
│  Electron / UI  │ ◄───────────────────► │   Go daemon      │ ──────────► │  agent CLIs     │
│  React 19       │                       │   127.0.0.1      │             │  (claude, codex,│
└─────────────────┘                       └──────────────────┘             │   cursor, …)    │
                                                   │                       └─────────────────┘
                                                   ▼
                                          ~/.crew44/  (plain-file state)

• Daemon — a single Go process at daemon/. Owns runtime discovery, agent/skill/chat state, and the JSON-RPC + event-stream surface. Auth is a per-launch bearer token; only /health is unauthenticated.
• Renderer — React 19 app in src/. Routes for Crew (agents, skills, runtimes), Tasks (chat threads with live streaming), New Task, Auto (suggestions), and Onboarding.
• Mobile — Expo app in packages/mobile/ pairs over an end-to-end encrypted Noise tunnel through a small relay, so you can read or nudge a running crew from your phone.

Privacy

• All UI, state, and orchestration happens on 127.0.0.1. Crew44 itself does not call out to any remote service.
• The only outbound traffic is whatever the underlying coding-agent CLI you chose (claude, codex, …) makes on its own — including the on-demand headless browser, which fetches its Playwright package and Chromium via npm and visits the URLs the agent navigates to.
• Mobile pairing, when enabled, uses a relay for NAT traversal, but the payload is end-to-end encrypted with Noise, so the relay only sees ciphertext. You can self-host the relay if you prefer; the URL is configurable.
• No analytics, no error reporting, no phone-home.

Getting started

Prerequisites

• macOS, Windows, or Linux
• Node 20+ and Go 1.26+
• At least one coding-agent CLI installed (claude, codex, cursor, …)

Run the desktop app

npm install
npm run dev

This builds the Go daemon, starts Vite, launches Electron, and connects the renderer once the daemon reports healthy.

Project layout

.
├── electron/              Electron main process, preload, app assets
├── src/                   React renderer
├── packages/mobile/       Expo mobile app
├── daemon/                Go module
│   ├── cmd/crew44-daemon  daemon entrypoint
│   ├── internal/          app, rpc, httpapi, store, runtime, agent adapters
│   └── test-utils/
├── docs/                  manual e2e harnesses + design notes
└── public/                renderer static assets

Development

npm run dev      # development app
npm run build    # renderer build + local app
npm run web:dev  # daemon + bare Vite development server
npm run test     # Go tests + renderer tests + mobile tests
npm run clean    # remove local build artifacts

Daemon configuration via env vars:

When auth is enabled, /rpc requires WebSocket subprotocols:

new WebSocket("ws://127.0.0.1:8080/rpc", [
  "crew44.rpc.v1",
  `crew44.bearer.${token}`,
])

See the JSON-RPC method list and skill-injection walkthrough in docs/.

License

MIT © 2026