跪拜 Guibai
← All articles
DeepSeek

A Multi-Model Roundtable Plugin Where DeepSeek Hosts a Debate Between Claude, Qwen, and Kimi

By 9931666 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Multi-model orchestration shifts AI from answer generation to perspective generation, but cost and coordination complexity have kept it experimental. This plugin gives a single developer a working roundtable with built-in cost controls, persistent state, and a human veto point — making multi-agent debate practical inside an existing chat harness.

Summary

Instead of getting one answer from one model, a new open-source plugin for DeepSeek Harness assembles a ring of vendor-diverse expert agents — Claude, Qwen, Kimi, MiniMax, GLM — around a DeepSeek host. One sentence in chat triggers automatic meeting creation, role assignment, and topology wiring. Experts debate with independent personas and per-round token budgets; when they deadlock, the meeting pauses and surfaces a human decision card.

The v0.2.0 release adds a visual expert management UI with real vendor logos, an on-demand knowledge base that avoids bulk token waste, per-expert output caps and opinion limits to control cost, and persistent meeting state that survives restarts. The plugin registers 13 roundtable tools on the host side, and each expert runs as a continuable sub-agent that can use a different model provider.

Under the hood, state lands in atomic JSON/JSONL files per meeting, and three token-saving mechanisms — budget circuit breakers, max-token caps, and host-relayed knowledge retrieval — keep multi-model sessions from burning through quota. The whole thing is MIT-licensed and mounts into any DSH web profile.

Takeaways
A single chat command like "hold a roundtable to discuss our cold-start plan" triggers automatic meeting creation, expert assignment, and topology wiring.
Each expert is a continuable sub-agent that can run a different vendor model (DeepSeek, GLM, Qwen, Kimi, MiniMax, Claude) with its own persona and role rules.
When experts reach an irreconcilable deadlock, the meeting pauses and presents a human decision card with options; the user picks, and the meeting resumes.
Per-expert token caps and per-round opinion limits act as budget circuit breakers — exceeding the cap automatically mutes that expert.
A knowledge base folder can be registered; the host reads and relays files on demand per expert request rather than dumping the entire library into context.
Meeting state persists to disk as atomic JSON/JSONL files and survives DSH restarts; historical meetings remain browsable.
The plugin registers 13 roundtable_* host-side tools and a global system prompt protocol that teaches the host when and how to orchestrate a roundtable.
The UI now includes drag-to-connect debate channels, real vendor logo avatars, and a management panel that keeps UI changes in sync with the host's awareness via a behavior document.
Conclusions

Treating disagreement as a first-class information source rather than a failure mode is a genuine shift from single-model answer generation — the debate structure itself produces signal.

The human decision card is the load-bearing piece: it prevents infinite loops and keeps authority explicit, which is what most multi-agent demos lack.

Token-saving here is not an afterthought — the three mechanisms (circuit breaker, per-round caps, host-relayed knowledge) are designed for multi-model economics from the start, which is rare in hobbyist agent projects.

Persisting meeting state as atomic files per meeting and decoupling it from process lifetime makes the plugin restart-resilient without a database, a pragmatic choice for a local-first tool.

Concepts & terms
DeepSeek Harness (DSH)
A chat harness that wraps DeepSeek models and supports a Cordis plugin system, allowing extensions to add tools, sub-agents, and custom UI panels.
Continuable sub-agent
An independent agent instance that can run a different model provider, maintain its own persona and conversation context, and be paused/resumed across multiple rounds of a larger orchestrated session.
Cordis plugin
DSH's dual-end plugin architecture (Host + Client) where the host side registers tools and system prompts, and the client side renders UI components using TypeScript, React, and CSS Modules.
Budget circuit breaker (token meltdown)
A cost-control mechanism that automatically mutes an expert agent when its output exceeds a configured per-round token limit or opinion count, preventing runaway spend in multi-model sessions.
From the discussion
Featured comments
咬代码的兽 1 likes

Making disagreement itself into information — that concept is great. The per-round token cap plus auto-mute is very practical; multi-model meetings burn money at an astonishing rate, and having a human decision card as the fallback makes sense — machines argue, humans make the final call. Recently on ai345 I've seen quite a few discussions about multi-agent collaboration approaches; the roundtable model feels like it could be a trend this year.

9931666  · 1 likes

Can you recommend a few that are novel? Or ones you're particularly interested in — I'll go study them.

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗