Crew44 CLI
A desktop app where Claude Code, Codex, Gemini and other agents work as a team of specialists in a shared project
- 358 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Launches installed console agents that write files and run commands in the projects you choose
- The built-in browser downloads Playwright and Chromium and visits addresses the agent names
- Mobile pairing passes a stream through an external relay until you host your own
Install
- Works in
Manual install
git clone https://github.com/getcrew44/crew44.git && cd crew44 && npm install && npm run devBuild from source: needs Node 20 and Go 1.26 and at least one installed console agent.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Launches installed console agents that write files and run commands in the projects you choose
- The built-in browser downloads Playwright and Chromium and visits addresses the agent names
- Mobile pairing passes a stream through an external relay until you host your own
This is third-party code. Review the repository files before installing.
What it does
Crew44 finds the console agents installed on your machine and builds a team from them. It supports eleven agents, from Claude Code and Codex to Gemini CLI and Qwen Code. For each member you set a role and an instruction, as well as a model and skills. The default crew has four roles: Partner, Engineer, Product Lead and Designer. Inside a project work happens in chats, and agents hand the turn to each other: one emits a handover marker with a short brief and the next continues from there. A planner drafts while an engineer codes and a reviewer checks the result. Each role can have its own model, for example one for plans and another for code. A chat can run in an isolated git worktree on a crew/… branch, which leaves your working copy untouched. A skill is written once as SKILL.md and attaches to any agent on any provider. A task can carry a goal: the crew turns it into a locked checklist of criteria, and a separate verifier in a fresh session without the chat history confirms every item before you accept the work. State lives as plain files in ~/.crew44.
Who it is for. For developers who already use several coding agents and want to split roles between them without juggling terminal windows.
Good fit when
- You want one model to plan, another to code and a third to review, all inside one project
- You need one skill set that works the same in Claude Code, Codex and Gemini CLI
- You want an independent verifier in a fresh session to confirm the done criteria one by one
- You want to watch running work from a phone through the mobile app
Not a fit when
- No console agent is installed on the machine: Crew44 does not run models itself and only manages them
- You need a single agent in the terminal without an interface: Claude Code or Codex alone is enough
- You need a ready build for an Intel Mac or Linux x64: there are none in the downloads
- You want to run the crew on a server without a graphical shell: the main flow is the Electron app
Example request
Have Product Lead write the done criteria for CSV export, Engineer implement it on a separate branch, and the verifier go through each criterionLimitations
- Ready builds exist for macOS on Apple Silicon (dmg), Windows x64 (exe) and Linux ARM64 (AppImage and deb). Building from source needs Node 20 and Go 1.26.
- Crew44 itself ships no models and uses your installed CLIs and their subscriptions or keys. Outbound traffic comes from those agents.
- The built-in headless browser downloads the Playwright package and Chromium through npm on first use.
- The mobile app connects to the computer through a relay with Noise encryption. The relay address is configurable and you can host it yourself.
How to disable. Close the app and remove it the usual way for your system. State lives in ~/.crew44 and projects in Documents/Crew44 or the folder you chose: delete them if the data is no longer needed. Remove the crew/… branches in your repositories with git branch -D and the branch name. The agents Crew44 managed stay installed.
FAQ
Which agents does Crew44 support?
Claude Code, Codex, Cursor Agent, Gemini CLI, Hermes, Kimi, OpenCode, OpenClaw, Pi, Qoder and Qwen Code. The app discovers them by scanning the disk. For a new CLI, add an adapter in the daemon/internal/backendagent folder and it appears in the picker.
Is Crew44 paid and does it need an account?
No and no: builds download without an account, and there is no subscription or telemetry. The license is MIT.
How does Crew44 isolate the agent's work from my code?
A chat can turn on the worktree option. The crew then works in a separate git checkout, and your working tree stays untouched.
How is work passed between agents?
An agent adds a handover marker with a short brief to its reply. The next agent receives that brief rather than the whole context and carries on. Chat events are written to an append-only events.jsonl file.
What data leaves the machine?
Crew44 itself calls no servers: the interface and the daemon run on 127.0.0.1. Only your agents' traffic leaves, plus an encrypted stream through the relay if you enable mobile pairing.
Discussion
No questions or reviews yet.
Related
CLI toolsA skill that turns several Claude Code, Codex and Cursor windows into a team with a coordinator, shared registry and cross-review
A self-hosted runtime for coding agents: each crew in its own Linux container, wrapped in a control plane with roles and audit
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
A skill with 25 commands to audit and improve the prompts, tools and agent designs of a project in Cursor, Claude Code and Codex
A memory and coordination layer for coding agents: specs and issues live in git while agents work in parallel
Self-hosted system for a team of AI agents: org chart, tasks, budgets and oversight of Claude Code, Codex and OpenClaw
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Crew44 (this entry) | no | 358 | ||
| Claude Squad | no | 8,694 | a terminal app for parallel agent sessions, with no roles or shared skills | |
| opcode | no | 22,426 | a desktop interface for Claude Code alone with sessions and custom agents | |
| Ralph Orchestrator | no | not required | 3,190 | a CLI orchestrator that loops an agent until the task is done |
README in short
The project contrasts working with one agent against a team of specialists and explains its concepts in a separate table. Under the hood are an Electron interface and a Go daemon with its own set of environment variables.