DSH Market
C

Ccteam

by firstintent · firstintent/ccteam

Not a pluginunknownfresh

ccteam turns the coding agents you already run (Claude Code, Codex, Grok, Kimi, DeepSeek Harness) into one team — any session can spawn, dispatch, and collect work from any vendor on any machine, while you steer it all from Telegram, Lark, or a browser tab. 把你在用的编程 agent 编成一支团队,跨厂商跨机器派活,Telegram/飞书/网页统一指挥。

Install Ccteam

Installs but activates nothing: package.json has no `dsh.bundle` declaration, so `dsh plugin` warns and loads no config layer.

This repository is not a DSH plugin

Its package.json declares no dsh.bundle. In the official docs' own words, a package like this “still installs, but only as a plain dependency: dsh plugin prints a warning and activates no layer”. The install looks like it worked and nothing happens.

What it actually is: ccteam turns the coding agents you already run (Claude Code, Codex, Grok, Kimi, DeepSeek Harness) into one team — any session can spawn, dispatch, and collect work from any vendor on any machine, while you steer it all from Telegram, Lark, or a browser tab. 把你在用的编程 agent 编成一支团队,跨厂商跨机器派活,Telegram/飞书/网页统一指挥。 If that is what you came for, use it directly from the repository — it is just not something dsh plugin add can activate.

Before you run it

  • A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
  • Installing from git resolves a moving branch. Pin a commit — github:firstintent/ccteam#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key
Not required.
Network access
Not required at runtime.
Language
Rust

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
dsh.bundlemissingfatalpackage.json has no `dsh.bundle` key
Verdict reason
no dsh.bundle declaration — installs as a plain dependency only
package.json read
crates/ccteam-web/web/package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

Each coding CLI is brilliant alone but works in isolation — one terminal, one context, no colleagues: - **Claude Code** — plans the deepest - **Codex** — grinds long jobs without wobbling - **Grok** — answers fastest - **Kimi** — bulk work on a tiny bill - **Pi** — one CLI over many providers (`anthropic/…`, `openai/…`), on your own machine ccteam is the connective tissue they lack — identity, routing, delivery guarantees, guardrails, a cost ledger — and leaves *how* the team organizes itself to prompts you version. **1 · Remote control from Telegram / Lark** Paste a bot token once (Settings → Access) and the chat becomes a full console — completion notifications, HITL `[approve] [deny]` buttons, and shipped files all land in the same thread. Dispatch at midnight, close the laptop, find th

Topics

GitHub topics on this repository

More in Model Catalog Pi Ai

Ranked by similarity inside the cluster, not alphabetically