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 via Git or S3/OSS sync; 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 RAG 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 | 简体中文 | 繁體中文 | 日本語 | 한국어

Home	Channels

• 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 — share a team drive (teamclu-team/) over OSS or Git; 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 — full-text and embedding-based indexing and search
• Built-in editors — Markdown and HTML (Tiptap), code (CodeMirror 6), and an agent-first diff reviewer
• Local file operations — with per-operation permission management

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.

Download the installer for your platform from GitHub Releases — .dmg for macOS, .exe for Windows.

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.

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.

A team shares a dedicated team drive (teamclu-team/), not the whole workspace. During onboarding the owner picks one share mode, which is then locked server-side:

Sync is owned by the amuxd daemon: it keeps one global copy per team under ~/.amuxd/teams/<team_id>/, and each linked workspace gets a teamclu-team symlink into that copy.

Only the shared layer syncs — a whitelist .gitignore keeps everything else local:

• skills/ — shared agent skills
• .mcp/ — MCP server configuration
• knowledge/ — team knowledge base documents

Personal files and the rest of the workspace stay local.

• Git modes need working Git authentication (SSH key or HTTPS token).
• OSS sync can surface conflicts; resolve them from the team shared-files UI.
• Sync runs on app startup, and can be triggered manually from Settings → Team.

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 and, optionally, a LiteLLM proxy for shared AI budget management.

• Architecture — components, topology, and data model
• API contract — TeamClu Cloud API /v1
• Context map — how the repo is divided into bounded contexts
• Contributing — dev setup, testing, repo layout
• Security policy

We welcome contributions! See the Contributing Guide for details.

• 📝 Documentation & translation — no dev environment needed
• 🐛 Bug reports
• ✨ Feature suggestions
• 🔧 Frontend development
• ⚙️ Rust development

• 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)
• Search: Tantivy full-text + embeddings

MIT