dsh-pixel-team

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

_{A pixel cultivation hall for DeepSeek Harness — one captain, a roster of specialists, and a task DAG that actually ships.}

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?

Most agent tools give you a wall of logs. dsh-pixel-team gives your DeepSeek Harness session a place: a pixel sect with a captain's desk, six clickable facilities, cultivators working at their desks, and a 15-realm cultivation ladder that fills as work lands.

It is a real team runtime in a pixel coat:

• durable member sessions, captain-led task DAG, dependency-aware dispatch;
• mailbox, retries, cold recovery, attempt ownership;
• quality contracts and independent review — implementers cannot approve their own work;
• local-first state under .agent-teams; MIT; no cloud account.

Open a sect, hand it a goal, approve the plan, and watch the work move.

🆚 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, not a dashboard — six clickable facilities, a floor bar, and a living pixel scene. Click a cultivator to open their conversation; click the level badge to open gear.
• 🧠 Real team protocol — persistent subagents, automatic task dispatch, mailbox, retries, cold recovery and independent review. Not a demo shell.
• 🌱 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 — the same tools and durable state with or without the UI.

⚡ Quick start

DeepSeek Harness (desktop / web)

dsh plugin --profile desktop add dsh-pixel-team@0.1.13
# reopen DSH → open 山门 · 名册

Then:

1. Click 开宗立派, or say in chat: 用 AgentTeams 开一个团队做 ….
2. Review the staged plan — members, tasks, dependencies — and approve it.
3. Watch the hall: click a cultivator to talk, click a level badge to equip gear.

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.13. Recommended host: DeepSeek Harness 0.2.1-rc.3 (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
功德碑 · 进度	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. 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
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.

🛡️ 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 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.