Buzz × DeepSeek Harness
A DeepSeek Harness agent in your Buzz community
A local coding agent that answers mentions in your channels and works in your repository. About 15 minutes, once per person.
Setting up a whole team? Start with the team starter: Team Pack, both plugins and a short path for new teammates, designers and developers.
One command
Checks this Mac, fetches the plugin, and opens the two download pages. It does not install anything for you or ask for a password.
curl -fsSL …/setup.sh | sh
Prefer to read it first? Download setup.sh and open it in an editor.
Steps
-
Install Buzz and join the community
Download Buzz, sign in with Builderlab, then open the community invitation your team sent you.
-
Install DeepSeek Harness
Download the desktop app and sign in (or configure your provider under Settings → Models). You do not need the
dshCLI. -
Install the plugin
Open the pinned install link. Buzz shows a preview; review the access and install. It asks for one process, a loopback MCP server, and read-only files.
If the button does nothing, download the zip, unzip it, and use Settings → Plugins → Manage plugins → Add → Add from folder.
-
Create your agent
Agents → New agent → DeepSeek Harness. Set Workspace to your repository, leave Launch command as
dsh, and keep Tool permissions on Allow.Open the agent's Settings → Test connection.
-
Say hello
In a channel or Solo chat:
@DeepSeek-Harness list the top-level folders and summarize AGENTS.md
0 of 5 done
Check the result
Paste the line from Test connection. This page only reads it locally.
If something is off
did not start …
Buzz cannot find or start DeepSeek Harness. Install the desktop app and rerun the check; the bundled command is found automatically.
the provider is not signed in
Open DeepSeek Harness and sign in, or configure the provider and key under Settings → Models.
The agent never answers my mention
Run Test connection first. A failed or cancelled turn leaves a ⚠️ notice in the conversation with the real error.
A teammate's mention does nothing
That is expected. Your agent only acts for you, its owner. Each person runs their own.
Tools are refused
Set the agent's Tool permissions to Allow, and make sure MCP was allowed when installing the plugin.
Download the check script and run sh onboard-check.sh for a per-piece report.
For the person inviting the team
| Send | Where to get it |
|---|---|
| Community invite | Buzz → Settings → Membership → Invite members → Invite with a link |
| This page | The deployed URL |
| Pinned plugin link | npm run install-link -- --repository … --ref v0.1.0 --commit <sha> |
| Plugin zip (fallback) | The download button in step 3 |
Ask every teammate to paste their Test connection line before their first real task. One line catches most setup problems.