dsh-pixel-team

dsh-pixel-team

Your agents don't need another dashboard.
They need a place to work.

_{A permanent pixel sect in your DeepSeek Harness sidebar — approve the plan, and a captain with a real roster ships the work, then shows it to you in place.}

English (default) · 简体中文

开宗 → review the plan → approve → watch the hall run.

▶ Live product page  ·  real DSH session screenshots below

⭐ If this is the agent UI you wanted to exist, star it — that's how the hall keeps growing.

🎬 A real session, not a mockup

_{Approve before spawn — 3 members, 3 tasks, 2 dependencies; nothing starts until you confirm.  ·  Live task DAG — the captain dispatches t1; 毒修 waits for t1, 体修 waits for t2.}

_{Gear that shows up — equip a flying sword and the captain actually rides it; artifacts, mounts and skills unlock by realm.}

_{One sect, three cultivators — role, realm, model at a glance.  ·  15 realms — 凡人 to 道祖.  ·  History — completed tasks and the next 开宗.}

🐉 What is this?

dsh-pixel-team turns a DeepSeek Harness session into a working sect. You approve a plan; a captain splits it into a dependency-aware task DAG; specialists with fixed contracts ship it. The hall lives in the right sidebar and stays one click away — collapse it and it becomes a token you can drag anywhere.

Under the pixels it is a delivery governance layer, not a chat skin:

• staged plans — nothing spawns until you approve the roster, tasks, dependencies and acceptance;
• durable member sessions, dependency-aware dispatch, mailbox, retries, cold recovery and attempt ownership;
• quality contracts (objective / scope / acceptance / verify) with host re-run commands and an independent reviewer gate — implementers cannot approve their own work;
• real cost accounting per task, a delivery report, and a showcase that opens the shipped artifact in place;
• team state under .agent-teams/ in your workspace; local-first, MIT, no cloud account.

Found a sect, hand it a goal, approve the plan, watch the hall run — then let it show you the delivery.

🆚 Not another agent dashboard

	Typical agent UI	dsh-pixel-team
Who is working	log rows	cultivators at their desks
What is blocked	status text	merit stele + dependency edges
Review	optional	independent gate
Progress	a percentage	15 realms, gear and mounts
State	a cloud account	your workspace, local-first
Fun	none	honestly, a lot

✨ Why you'll love it

• 🏯 A hall that lives beside your chat — the sect sits in the right sidebar, not over your conversation. Collapse it to a token, drag the token anywhere, click it to bring the hall back — even from a conversation that has no sect yet.
• ⏹ Stop-and-run-now from the composer — when a task is stuck behind a long-running one, one button preempts the current task and starts the next ready one. Two clicks within three seconds, nothing lost.
• 🧠 Real team protocol — persistent subagents, dependency-aware dispatch, mailbox, retries, cold recovery and attempt ownership. Not a demo shell.
• 🧾 Delivery, not vibes — quality contracts, host re-run of every verify command, and an independent reviewer gate: implementers cannot approve their own work.
• 🖥 Delivery showcase — when work ships, the library opens the artifacts in place: pages run inside the panel, images render directly, source is readable. No installing, no starting a server, no commands to run yourself.
• 🌱 Cultivation that shows up — tasks and idle time feed a shared 15-realm ladder; gear, mounts and skills are drawn into the hall; crossing a realm gets a longer breakthrough effect.
• 📜 封神榜 + 宗门志 — a sect roll, realm ladder, cultivation card, support/community/about and feedback in one place.
• 🔒 Local-first & MIT — team state lives in your workspace. No cloud account, no hidden sync. One command, web + headless.

⚡ Quick start

DeepSeek Harness (desktop / web)

dsh plugin --profile desktop add dsh-pixel-team@0.1.133
# reopen DSH — the hall is waiting in the right sidebar

Then:

1. Click 开宗立派 — or collapse the hall to its token and click it. The founding wizard asks for the goal, doctrine, interview answers and sect.
2. Review the staged plan — members, tasks, dependencies, acceptance — and approve it. Nothing spawns before that.
3. Watch the hall run. Click a cultivator to open their conversation, click a level badge to equip gear, and open 藏经阁 → 展示 to see the delivered artifact in place — no commands to run.

From GitHub

git clone https://github.com/EternalNight996/dsh-pixel-team
dsh plugin --profile desktop add ./dsh-pixel-team

CLI / headless

dsh --profile desktop
# ask: 用 AgentTeams 开一个团队做 …

Package version 0.1.133. Recommended host: DeepSeek Harness 0.2.1-rc.5 (web + headless). Exact matrix: compatibility.json.

Prefer to look first? Open the live product page on the Mengyou website.

🏯 The hall

Facility	What it does
山门 · 名册	current sect, roster history and team entries
藏经阁 · 道统	members, task contracts, staged plans, founding wizard; the 展示 button previews delivered artifacts
功德碑 · 进度	task dependencies, dispatch progress, verification evidence
封神榜	sect roll, 15 realms, cultivation card, leveling tips, sect story
天机阁	equipment inventory: artifact / mount / skill, immediate hall preview
宗门志	support, community, about and a privacy-bounded feedback form
收件	captain inbox, keyboard reachable and text-escaped

The wall and the floor bar are two routes into the same panels. Collapse the hall and it becomes a draggable token; click the token to bring the right-sidebar hall back. Click a cultivator to open their conversation; click their level badge to open gear.

🧠 Under the pixels

• captain-led task DAG with dependency-aware dispatch;
• persistent member sessions, mailbox and attempt ownership;
• quality contracts: objective, scope, acceptance, verify, review verdict;
• independent verifier/reviewer gates, repair rounds and cold recovery;
• per-role contracts that keep frontend/backend/integrator work in disjoint layers;
• team state under .agent-teams/<teamId>/ — inspectable, local, yours.

🧩 Roles & templates

Template	Default roles	Best for
Full stack	integrator · frontend · backend · verifier · reviewer	contract-first features; parallel layers
Security hardening	auditor · security · verifier · reviewer	repro-before-fix, minimal diff, residual risk
Read-only audit	auditor · reviewer	evidence gathering without touching the workspace
Fix / feature / research / build / docs / debate	small role sets	everyday team work
Architecture	architect · implementer · verifier · reviewer	boundaries and migrations

Each specialist gets a fixed contract: ownership, must / must not, done, five-bullet report, and a working budget. The full-stack team is intentionally five people: the integrator owns both the contract and final integration, cutting one handoff.

🧾 Delivery, not vibes

Signal	Evidence
Full suite	pnpm verify exit 0
Browser-side contracts	pnpm verify:web-routes pass
Publish artifact	package smoke checks runtime + support QRs, excludes source/tests/docs
Real team run	captain dispatch → member writes → independent review → summary; see docs/agent-teams-real-model-verification.json
Isolation	implementers cannot approve their own implementation

This is a tool for parallel wall-clock + independent verification, not a promise that every task gets cheaper. Small tasks are usually better with one agent.

⚙️ Quality gate configuration

The plugin config field quality controls how gates are audited:

Option	Default	Effect
autoVerify	true	The host re-runs every declared verify command before accepting a completed quality task
autoReview	false	The host auto-completes ready review tasks after all gates, the target acceptance and host commands pass
requireAcceptance	true	Auto review requires every acceptance item of the reviewed task to pass
autoDetect	true	Detect the generated project's own package.json test/typecheck script and run it with the host verify
reviewMode	"auto"	auto: host closes the review; human: host audits then waits for a human "Confirm review" click in 藏经阁
commands	["git diff --check"]	Fallback verify commands for generated projects; plugin scripts are never inherited
commandsByProject	{}	Per-product verify commands keyed by root, e.g. "projects/snake": ["node projects/snake/smoke.mjs"]
verifyTimeoutMs	120000	Host timeout per verify command

Every field is optional; omitted fields use the defaults above (omit quality entirely to disable all overrides).

quality:
  autoReview: true
  reviewMode: "human"   # 宿主审核通过后停在「待人工复核」
  commandsByProject:
    "projects/贪吃蛇": ["node projects/贪吃蛇/smoke.mjs"]

🛡️ Boundaries

• No hidden cloud sync: cultivation and feedback diagnostics stay local.
• Approval is explicit: a staged plan does not start until you approve it.
• Deployment requires explicit confirmation; agents do not silently replace a running sect.
• Review is independent: an implementer cannot approve its own implementation.

🗺️ Roadmap

• more sect and role templates;
• deeper equipment, mount and skill effects in the hall;
• native app icon set for desktop / web / iOS / Android (in progress under assets/app-icons);
• more docs and translations;
• your idea — open an issue.

🧑‍💻 Development

pnpm install
pnpm typecheck
pnpm build
pnpm verify
pnpm verify:web-routes

Useful docs: release checklist, maintenance workflow, IP & attribution.

App icons live in assets/app-icons/ (desktop, web, iOS, Android) and the plugin ships assets/zhulong.ico / assets/zhulong-icon.png for app packaging.

💬 Community

Questions, ideas, or DSH plugin talk — join the QQ or WeChat group:

QQ group	WeChat group

Buy the author a coffee (optional):

WeChat Pay	WeChat Reward

Sponsorship is optional and changes nothing; the plugin stays MIT and free. See SPONSOR.md.

• Issues: https://github.com/EternalNight996/dsh-pixel-team/issues
• Maintained and published by 惠州市梦游科技有限公司 (Huizhou Mengyou Technology Co., Ltd.).

📄 License

MIT © 2026 惠州市梦游科技有限公司. See NOTICE.md and LICENSE for attribution and license text. The pixel hall, cultivation system, equipment, 封神榜 and 宗门志 are original to this project.

⭐ Star the repo if you want the hall to keep growing.