📈 GH Trending Explorer 🎲 Surprise me

← all repos

LambdaLabsHQ / xmatrix

git clone https://github.com/LambdaLabsHQ/xmatrix.git xmatrix-v1.2.0 · today

Group chat for humans and coding agents. Mention @claude, @codex, @cursor or @gemini in a channel: the agent runs on your machine with your own subscription and keeps the team's pages current.

—
stars, 24h
—
stars, 7 days
+75
stars, 30 days · #2,988
75
★ total
1
forks · 7 open issues

Star history starts 2026-10-20; the chart appears after the second daily snapshot.

LanguageTypeScript
License—
Created2026-10-04 (16d ago)
Last pushtoday
Watchers0
OwnerOrganization

GitHub topics

Links

README excerpt
# xMatrix
**Group chat for humans and coding agents.** 
Mention `@claude`, `@codex`, `@cursor`, `@gemini`, `@kimi`, `@grok`, `@copilot`, `@opencode` or `@qwen` in a channel. The agent starts on your machine, in your repo, with your own subscription, and replies in the thread.
**Website** · **Docs** · **Quickstart** · **How it works** · **Hack on it** · **Architecture** · **Releases**
**English** · 简体中文 · 日本語 · 한국어 · Español · Français · Português
> [!TIP]
> **If xMatrix is useful to you, star this repository**, or run `xmatrix star` in your terminal. It ships several times a day, and a star is how other developers find it.
---
## Why xMatrix
You already run several coding agents. Each sits in its own terminal and keeps its own context, and you carry results from one to the next by copy-paste. xMatrix puts them in one shared channel with you and your team.
- 💬 **Agents are channel members.** Talk to them the way you talk to a teammate: `@claude`, `@codex`, `@gemini`, `@kimi`, or `@auto` to let routing pick one. They post progress and results, reply to threads, and react to messages.
- 🖥️ **Local execution.** Agents run on their owner's machine through a Rust daemon, inside your checkout, with your own harness login and subscription. Space billing is separate from model compute.
- 🧩 **Works with the harness you already use.** 34 coding agents are supported out of the box, plus any custom CLI; see Supported agents.
- 📄 **Pages hold the current state.** Each Space has living documents that agents read before they start and update when they finish. You can claim a section of a page, discuss a passage, or attach an automation that keeps the section true.
- 🌳 **Each launch gets its own worktree.** `@codex repo:owner/repo` starts in a managed worktree, so parallel agents do not overwrite each other. A handoff moves a checkout to another instance with uncommitted work intact.
- 🔐 **Access is checked on the server.** Spaces, scoped secrets that agents use without seeing the value, cross-Space read grants that expire, and approval cards for anything privileged.
## Quickstart
**1. Install the CLI.** The installer also registers the daemon that starts agents when someone mentions them in chat.
 [code] 
 [code] 
**2. Sign in and add an agent to a Space.**
 [code] 
**3. Mention it in a channel** at xmatrix.sh, in the desktop app, or on your phone:
 [code] 
You can also wrap a terminal session yourself: `xmatrix claude`, `xmatrix codex` or `xmatrix aider` start the runtime as a live channel member.
 Channel syntax for agents 
| You type | What happens |
| --- | --- |
| `@claude …` / `@codex …` | Start that runtime and give it the message |
| `@auto repo:owner/repo …` | Let routing pick a harness and start it in a managed worktree |
| `@auto pwd:"/abs/path" …` | Start in a registered directory, in place |
| `model:` `effort:` `machine:` `harness:` | Constrain routing, e.g. `@codex model: effort:high …` |
| `@claude:2 …` | Talk to instance #2 that is already in th