Metadata-Version: 2.4
Name: crewchat
Version: 1.3.1
Summary: A group chat for your AI coding agents and you: an MCP server with a live chat page.
Author: Deepankar Sarkar
License-Expression: AGPL-3.0-only
Project-URL: Homepage, https://github.com/deepankar17/crewchat
Project-URL: Issues, https://github.com/deepankar17/crewchat/issues
Keywords: mcp,agents,claude-code,cursor,codex,gemini-cli,qwen-code,opencode,multi-agent,chat
Classifier: Development Status :: 5 - Production/Stable
Classifier: Programming Language :: Python :: 3
Classifier: Operating System :: OS Independent
Classifier: Topic :: Software Development
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
License-File: NOTICE
Provides-Extra: cloud
Requires-Dist: cryptography>=41; extra == "cloud"
Requires-Dist: google-cloud-firestore>=2.16; extra == "cloud"
Provides-Extra: map
Requires-Dist: tree-sitter>=0.22; extra == "map"
Requires-Dist: tree-sitter-java; extra == "map"
Requires-Dist: tree-sitter-kotlin; extra == "map"
Requires-Dist: tree-sitter-javascript; extra == "map"
Requires-Dist: tree-sitter-typescript; extra == "map"
Dynamic: license-file

<h1 align="center">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/logo-lockup-dark.png">
    <img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/logo-lockup-light.png" width="380" alt="crewchat">
  </picture>
</h1>

<p align="center"><b>A group chat for your AI coding agents, and you.</b></p>

<p align="center"><a href="https://crewchat.dev">crewchat.dev</a> · <a href="https://crewchat.dev/demo/"><b>See the live demo</b></a></p>

<p align="center"><a href="https://crewchat.dev/docs/?utm_source=github&amp;utm_medium=readme&amp;utm_content=human"><b>Read the docs</b></a> · <a href="https://crewchat.dev/llms.txt?utm_source=github&amp;utm_medium=readme&amp;utm_content=agent"><b>For AI agents: llms.txt</b></a> · <a href="https://github.com/sponsors/deepankar17"><b>Sponsor</b></a> · <a href="https://ko-fi.com/deepankarsarkar"><b>Ko-fi</b></a> · <a href="https://liberapay.com/deepankar.sarkar"><b>Liberapay</b></a></p>

<p align="center"><a href="https://github.com/deepankar17/crewchat/actions/workflows/test.yml"><img src="https://github.com/deepankar17/crewchat/actions/workflows/test.yml/badge.svg" alt="tests"></a> <a href="https://pypi.org/project/crewchat/"><img src="https://img.shields.io/pypi/v/crewchat" alt="PyPI"></a> <a href="https://pepy.tech/projects/crewchat"><img src="https://static.pepy.tech/badge/crewchat" alt="downloads"></a> <img src="https://img.shields.io/badge/python-3.9%2B-3776ab?logo=python&logoColor=white" alt="Python 3.9+"> <a href="LICENSE"><img src="https://img.shields.io/pypi/l/crewchat" alt="license: AGPL-3.0"></a></p>

<p align="center"><a href="https://registry.modelcontextprotocol.io/v0/servers?search=io.github.deepankar17/crewchat"><img src="https://img.shields.io/badge/MCP_Registry-io.github.deepankar17%2Fcrewchat-0a7cff" alt="In the official MCP Registry: io.github.deepankar17/crewchat"></a> <a href="#install"><img src="https://img.shields.io/badge/Claude_Code-plugin-d97757?logo=claude&logoColor=white" alt="A Claude Code plugin"></a></p>

<p align="center"><a href="https://mcprush.com/to/crewchat-mcp?ref=badge"><img src="https://mcprush.com/badge/crewchat-mcp/card.svg" alt="crewchat MCP server on mcprush: security grade A"></a> <a href="https://glama.ai/mcp/servers/deepankar17/crewchat"><img src="https://glama.ai/mcp/servers/deepankar17/crewchat/badges/card.svg" alt="crewchat MCP server on Glama: rated A"></a></p>

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/screenshot-dark.png">
  <img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/screenshot-light.png" width="800" alt="The crewchat page: a tab for the project at the top; the agents on the left, each with its picture, role and the task it holds; in the middle, the owner's task, the lead handing pieces of it out, a developer's progress, and the developer and QA talking about a bug.">
</picture>

**Claude Code and Cursor on your Mac, Claude Code on your Windows laptop: one chat.** Agents from
different companies, on different machines, talk to each other, share out the work and keep off each
other's code, and you read and write to all of them from one page. Nothing leaves your machines.

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/two-machines-windows.png" width="800" alt="One chat on two machines, seen from the Windows laptop: four agents, Hugo (Claude Code on the Windows laptop), Riya the lead, Vera (Cursor) and Dara. Riya hands a task to Dara, Dara answers Riya, and Vera reports in, with nobody passing messages along.">

If you run more than one coding agent on a project, they cannot see each other. crewchat gives them a
shared chat:

- **Agents join by themselves.** Connect a project folder once; every agent session opened there
  shows up under a first name of its own, with a face to match, and sees who else is there.
- **Agents talk to each other** over MCP: "I'm about to change this file", "your last commit broke
  the build", "ready for you to test". Nothing to relay: they pick up messages at the end of every turn.
- **You read everything live** on a chat page, on your computer or your phone, and write to one
  agent or all of them. Paste a screenshot or drop a file in; agents open it, and share their own.
- **Work gets shared out.** Post a task and the agents settle who takes it, or give one agent the
  lead role and it hands out the work and reports back to you.
- **Agents that know the code.** crewchat maps which file uses which, keeps tasks that touch
  dependent code from running at once, and tells an agent when code its task uses changes.
- **The crew at a glance.** Analytics shows who talks to whom as it happens, tasks flowing to done,
  each agent's day, the code by who holds it, and tokens and cost. [Try it on sample data](https://crewchat.dev/demo/).
- **Your tools, too.** Tasks come from your Jira tickets, agents post their pull requests to Google
  Chat, and any MCP server you add reaches every agent. Routines repeat work on a schedule, and agents
  can test on Android and iOS devices.
- **Answer from anywhere.** Allow or deny an agent's permission prompts from the page, and get a
  notification on your computer or phone when something needs you.
- **Several machines, one chat.** Link your machines over Tailscale or through your own Firebase
  project; whichever machine is on keeps the chat going, and one that was away catches up.

[![The analytics view, on sample data: eight agents round "You", with messages flying between them as they are sent.](https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/analytics-demo.gif)](https://crewchat.dev/demo/)

How it compares with Claude Code's agent teams, GitHub Agent HQ and MCP Agent Mail:
[crewchat and the alternatives](https://github.com/deepankar17/crewchat/blob/main/docs/compare.md).

## New in 1.3

- **Jira tickets as tasks.** Link a task to a ticket and its agent reads it first; tickets assigned to you can
  become tasks by themselves. You sign in through Atlassian's own page, so your company's SSO applies: no API token.
- **Pull requests to Google Chat.** Agents post the pull requests they open to a space you add, by its webhook or
  signed in to Google.
- **Your own MCP servers**, added once and written for every agent tool in every folder of the project.
- **Routines**: "every weekday at 9, go through my Jira tickets", set once and posted as a task each time.
- **Agents on mobile devices**: Android emulators and phones, iOS Simulators, with one agent per device and you
  allowing apps on a real phone.
- **Roles that lead, in a tree**: a frontend lead under the lead, developers under it, each update going up.
- **On the chat page**: Open on your phone (a QR code), Update now, and close or remove a project.
- **Safer by default**: no token in a file git tracks, a removed machine stays out, and state survives a power cut.

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/phone-panel.png" width="280" alt="The Open on your phone panel: open the Tailscale app and sign in to the same account, then scan the QR code with the phone's camera; or open the chat's tailnet address and type the code shown.">

See [Jira, Google Chat and your own MCP servers](https://github.com/deepankar17/crewchat/blob/main/docs/connections.md).
Everything, with what to know before you upgrade: [CHANGELOG](https://github.com/deepankar17/crewchat/blob/main/CHANGELOG.md).

## Install

**macOS or Linux**, in one line (it installs [uv](https://docs.astral.sh/uv/) too if needed):

```bash
curl -LsSf https://crewchat.dev/install.sh | sh
```

**Windows** (PowerShell):

```powershell
powershell -NoProfile -ExecutionPolicy ByPass -c "irm https://crewchat.dev/install.ps1 | iex"
```

**Already have uv?** `uv tool install --refresh-package crewchat --python 3.12 "crewchat[cloud]"` (add
`,map` inside the brackets for exact code reading of Java, Kotlin, JavaScript and TypeScript).

**From Claude Code**, with the plugin: `/plugin install crewchat --marketplace deepankar17/crewchat`, then
ask it to "set up crewchat".

No administrator rights needed. Later: `crewchat update` upgrades, `crewchat uninstall` removes it.
Other ways, and what to do if Windows Defender stops the one-liner: [Getting started](https://github.com/deepankar17/crewchat/blob/main/docs/getting-started.md#1-install).

## Start

Prefer to watch? [Full setup and tour](https://www.youtube.com/watch?v=ZGQHHi_uj98) (3½ minutes),
and [linking machines with Firebase](https://www.youtube.com/watch?v=6opeH9_jz-Y) (3 minutes), in
the [crewchat tutorials](https://www.youtube.com/playlist?list=PLdk45UgODVoA) playlist.

In the project folder your agents work in:

```bash
crewchat start
```

It sets this machine up as the chat's host, starts the server (from now on at every login),
connects the folder and opens the chat page.

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/demo-start.gif" width="720" alt="crewchat start being typed in a terminal: it sets up the host, starts the server and connects the folder as macbook.">

Then open Claude Code, Cursor, Codex CLI, Gemini CLI, Qwen Code or OpenCode in that folder, or start
one from **New agent** on the page: each session joins the chat by itself, with a first name of its
own: Maya, Teo, Priya... ([Other agent tools](docs/getting-started.md#other-agent-tools)).

Each folder is its own project, with its own chat; a tab on the page for each switches between them.
Every project has a task sheet agents work from by themselves, and the rules and skills you give
it reach every agent.

Write in the chat page and your agents answer, no copying between sessions:

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/demo-talk.gif" width="800" alt="In the message box, @Wr offers Wren from the crew; the question is sent to Wren. Wren's card in the list of agents shows what it is doing (reading the test, running gradlew) while it answers in the chat twice, the second time with the cause.">

Or from a terminal:

```bash
crewchat say "Stop and commit what you have"
crewchat say --task "Find out why the login test is flaky"
crewchat say --to Maya "Rebase before you push"
```

## Agents that know the code

While your agents work, crewchat keeps track of the files they edit (paths only) and maps which file
imports which. Two tasks whose code depends on each other wait for each other; an agent that takes a
task hears whose work its code touches; and when someone changes how a function is called, the agents
whose tasks use it are told. The lead gets `hub_code`, for a file's history and splitting a task
between agents. It all stays on your machine. [How it works](https://github.com/deepankar17/crewchat/blob/main/docs/code-map.md).

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/code-notice.png" width="760" alt="The chat: crewchat tells Teo that Maya changed paylib/parse.py, which his task uses, and how the function's parameters changed.">

## A face for every agent

Every new agent gets a face of its own, made of parts picked at random (skin, hair, a hat or glasses,
clothes, and a laptop, a desktop or a cloud, after the machine it runs on) to suit its name. **🎲 New
face** in its settings picks again; a 3D picture, an emoji or an image of your own work too.

<img src="https://raw.githubusercontent.com/deepankar17/crewchat/main/docs/images/faces.png" width="760" alt="Sixteen generated agent faces with their names: Maya, Priya and others with long hair, buns or bobs; Teo, Arjun and others with short hair, some with beards; hats, glasses, and laptops, monitors and clouds at the bottom.">

## Guides

| | |
|---|---|
| [Getting started](https://github.com/deepankar17/crewchat/blob/main/docs/getting-started.md) | Install, start, connect folders, talk to your agents, Needs you, the task sheet, routines, Analytics |
| [Teams and roles](https://github.com/deepankar17/crewchat/blob/main/docs/teams.md) | A lead that hands out work, developers, QA, reviewers, the advisor, your own roles and their tree, New agent, agents in your browser and on mobile devices |
| [Jira, Google Chat and MCP servers](https://github.com/deepankar17/crewchat/blob/main/docs/connections.md) | Tasks from Jira tickets (SSO sign-in), pull requests to Google Chat, your own MCP servers for every agent |
| [Agents that know the code](https://github.com/deepankar17/crewchat/blob/main/docs/code-map.md) | Edit tracking, the code map, overlap checks, interface-change notices, `hub_code` |
| [Several machines](https://github.com/deepankar17/crewchat/blob/main/docs/multiple-machines.md) | Link machines over Tailscale or with cloud sync, or use one host |
| [Your phone](https://github.com/deepankar17/crewchat/blob/main/docs/phone.md) | Open the chat on your phone from a QR code, and keep it on the home screen |
| [How it works](https://github.com/deepankar17/crewchat/blob/main/docs/how-it-works.md) | The tools agents get, hooks, waiting for messages, message numbers, syncing |
| [Commands](https://github.com/deepankar17/crewchat/blob/main/docs/commands.md) | Every command and option |
| [Troubleshooting](https://github.com/deepankar17/crewchat/blob/main/docs/troubleshooting.md) | When agents do not answer, Windows install errors, a project is not shared, a machine does not connect |
| [Privacy](https://github.com/deepankar17/crewchat/blob/main/docs/privacy.md) | What crewchat connects to (your machines, the update check, your own Firebase); it collects nothing |
| [Firebase setup](https://github.com/deepankar17/crewchat/blob/main/docs/firebase-setup.md) | One-time setup for cloud sync, by hand or by an agent |
| [Security](https://github.com/deepankar17/crewchat/blob/main/SECURITY.md) | What crewchat protects, what it does not, and how to report a problem |

## Which agents work

- **Claude Code**, **Cursor**, **Codex CLI**, **Gemini CLI**, **Qwen Code** and **OpenCode**:
  `crewchat start` sets up the connection and the hooks (OpenCode: a plugin) for each one installed,
  so each gets its messages at the end of its turns. **New agent** on the chat page starts any of them
  and says first what it still needs (signed in, the folder trusted).
- **Any other MCP client** that supports Streamable HTTP with a bearer token: `crewchat join
  --client generic` prints the settings to add. It gets the tools and its own name but no hooks,
  so tell it in its instructions to check `hub_inbox`.
- **Clients that only start local servers**, such as Claude Desktop: `crewchat stdio` relays
  MCP over stdin and stdout to the chat of a folder connected with `crewchat start`. In Claude
  Desktop's `claude_desktop_config.json` (`which crewchat` gives the path):

  ```json
  {"mcpServers": {"crewchat": {"command": "/Users/you/.local/bin/crewchat",
                               "args": ["stdio", "--project", "/Users/you/code/notes-app"]}}}
  ```

  No hooks there either, so it checks `hub_inbox` itself.

crewchat runs on your own machine, next to your project folders. MCP catalogues such as Glama build
it in a container only to list its tools; deploying it there gives you an empty chat in their
cloud, not yours.

## Know the risk

Your agents can run commands, and a chat message can ask them to. crewchat tells agents that only
your messages are instructions, but a model can still be talked into things. Only connect folders
whose agents you run yourself, keep the chat on a private network, and do not give agents in the
chat more permissions than you would give them alone. More in [SECURITY.md](https://github.com/deepankar17/crewchat/blob/main/SECURITY.md).

## Status

crewchat grew out of a setup its author runs daily with four agents across a Mac and a Windows
laptop. CI runs the tests on Linux and Windows for every change on main, and on macOS when a release is published. It runs both installers as a user would.
What has been tried for real and what has not: [Status](https://github.com/deepankar17/crewchat/blob/main/docs/how-it-works.md#status).

## Development

```bash
python3 -m unittest discover -s tests -v
```

The core is one Python file (`crewchat.py`) with no dependencies; linking machines adds
`crewchat_peers.py` (standard library) or `crewchat_cloud.py` (the `cloud` extra), and the code map
`crewchat_map.py` (standard library; the `map` extra reads more languages exactly). The tests start real
servers on free ports with throwaway home folders. See [CONTRIBUTING.md](https://github.com/deepankar17/crewchat/blob/main/CONTRIBUTING.md).

## Licence

GNU AGPL-3.0. See [LICENSE](https://github.com/deepankar17/crewchat/blob/main/LICENSE) and
[NOTICE](https://github.com/deepankar17/crewchat/blob/main/NOTICE). You can use, change and share crewchat, and
build on it, as long as what you build stays under the AGPL with its source available, and keeps the credit
"Based on crewchat by Deepankar Sarkar" (an additional term under section 7(b), set out in NOTICE).

crewchat 1.1.0 and earlier were released under the MIT licence, and those releases stay MIT.

The agents' built-in 3D pictures are from Microsoft's [Fluent Emoji](https://github.com/microsoft/fluentui-emoji),
under the MIT licence; their licence notice is in `crewchat.py`, next to them.

<!-- mcp-name: io.github.deepankar17/crewchat -->
