TeamClu
Local AI agents — your AI Ally for every role
Your Ally. Together.
- 👥 Built for teams — share Skills, Knowledge, and MCP config across the whole team; each member keeps their own private context
- 🎭 Skills × Roles — a composable role library lets the same agent specialize for sales, support, ops, engineering, or whatever your team needs
- 🔋 Batteries included — built-in team knowledge base, Auto UI understanding, speech-to-text, and six channel gateways (WeCom, Feishu, Discord, Kook, WeChat, Email) — no glue code
- 🧑💻 Solo builders to SMBs — local-first, private by default; scales from a single user to a small company
English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Bahasa Indonesia
Screenshots
Features
- Three-column workspace — sidebar, chat, and detail panel
- Local agent runtime — agents run on your machine, hosted by the
amuxd daemon
- Channel gateways — reach your agents from Discord, Feishu, Email, Kook, WeCom, and WeChat
- Automation — scheduled tasks via cron
- Team collaboration — sync team knowledge and documents through S3-compatible object storage; see Team collaboration
- MCP support — connect agents to enterprise systems via the Model Context Protocol
- Skills / plugins — extend agents with workspace-level and global skill sources
- Knowledge base — a Markdown vault synced across the whole team, with path-level ACL and version history
- Built-in editors — Markdown and HTML (Tiptap), code (CodeMirror 6), and an agent-first diff reviewer
- Local file operations — with per-operation permission management
How it works
TeamClu is split into a client layer, an agent host, and a cloud backend:
Desktop (Tauri) iOS Mobile (Expo) Chrome extension
│ │ │ │
└──────────────┴─────┬──────┴──────────────────┘
│
┌──────────────┴───────────────┐
│ TeamClu Cloud API │ identity, teams,
│ (/v1) │ sessions, messages
└──────────────┬───────────────┘
│
┌────────┴────────┐
│ amux daemon │ agent host + channel gateways
│ (amuxd) │ + team sync (git / OSS)
└────────┬────────┘
│ HTTP / RPC
┌────────┴────────┐
│ local agents │ opencode (default), …
└─────────────────┘
- Clients own the UI and local files. Installing TeamClu Desktop also installs the
amuxd daemon, so your machine is an agent host out of the box.
- amuxd hosts local agent backends, runs the channel gateways, and owns team sync. It can also be installed standalone on a server, with no GUI.
- Cloud API (
/v1) is the only backend clients talk to. See docs/openapi/teamclu-api.v1.yaml for the contract, and docs/architecture/v2.md for the full architecture.
Clients
| Client | Path | Status |
|---|
| Desktop (macOS / Windows / Linux) | apps/desktop/ + packages/app/ | Primary client |
| iOS | apps/ios/ | Native SwiftUI, ships via TestFlight |
| Mobile (iOS / Android) | apps/expo/ | Expo; onboarding and sessions |
| Chrome extension | apps/extension/ | MV3 |
Install
Download the installer for your platform from GitHub Releases — .dmg for macOS, .exe for Windows.
macOS "damaged" warning
If macOS reports the app is "damaged" or "cannot be opened because the developer cannot be verified", that's Gatekeeper reacting to an unsigned download. Clear the quarantine attribute:
xattr -cr /Applications/TeamClu.app
This step isn't needed for builds signed and notarized with an Apple Developer certificate.
Quick start (development)
Prerequisites: Node.js >= 20, pnpm >= 10, Rust >= 1.70
pnpm install
pnpm tauri:dev
After launching, pick a workspace directory in the TeamClu UI.
To skip the first-run wizards during development:
pnpm tauri:dev -- --skip-setup --skip-daemon-onboarding
For the frontend alone (no Rust build), run pnpm dev. Build commands, the shared Rust build cache, the test suites, and the repo layout are covered in the Contributing Guide.
Team collaboration
A team shares a few dedicated directories, not the whole workspace. Sync goes through S3-compatible object storage (Alibaba OSS / WebDAV) — there is no Git mode.
Sync is owned by the amuxd daemon: it keeps one global copy per team under ~/.amuxd/teams/<team_id>/, and each linked workspace surfaces the synced roots as symlinks.
What gets shared
Only the synced roots leave your machine; the rest of the workspace stays local:
team-knowledge/ — the team knowledge baseteam-documents/ — team documents (files have an owner and access can be restricted)
Team skills and team MCP servers no longer travel in this tree: skills come from the skills registry, MCP servers and team env from the Cloud API.
Notes
- Sync runs on app startup, and can be triggered manually from the team share column in the sidebar.
- Conflicts surface there too, and are resolved in the main panel.
Configuration
Build-time configuration lives in build.config.*.json at the repo root, merged in this order:
build.config.json → build.config.${BUILD_ENV}.json → build.config.local.json
Copy the example to get started:
cp build.config.example.json build.config.local.json
The key setting is cloudApiUrl, which points the app at a TeamClu Cloud API deployment:
{
"cloudApiUrl": "https://api.teamclu-dev.ucar.cc",
"features": {
"channels": { "discord": true, "feishu": true, "email": true }
}
}
build.config.local.json is git-ignored. For local development you can also override the endpoint with VITE_CLOUD_API_URL in packages/app/.env.local. Rebuild for changes to take effect.
The Cloud API implementation lives in services/fc/ (Node.js 20), backed by Supabase, with the team AI gateway in services/ai-gateway/ handling shared AI budgets.
Documentation
Contributing
We welcome contributions! See the Contributing Guide for details.
Tech stack
- Desktop: Tauri 2.0 (Rust)
- Daemon: Rust (
amuxd), local agent backends (opencode HTTP, …)
- Frontend: React 19 + TypeScript, Tailwind CSS 4, Zustand
- iOS: SwiftUI + SwiftPM (
AMUXCore)
- Editors: Tiptap (Markdown / HTML), CodeMirror 6 (code), Shiki (highlighting)
License
MIT
