DSH Mesh

三个立刻能用的例子

不是"远程执行"，是 agent 之间互相派活：你说要什么结果，对端的 agent 自己决定怎么做。

链式也可以：A 派给 B 编译，B 做完再交给 C 部署验证，最后结果回到 A。

Three things you can do today

Not remote execution — agents handing work to each other. You say the result you need; the other agent decides how.

Chains work too: A sends to B to compile, B hands it to C to deploy, and the result comes back to A.

它能帮你做什么

以前：两台机器各干各的，你在中间搬上下文、复述需求、复制结果。现在：一句话派过去，对端的 agent 自己开跑，结果由它派回来。

What it is for

Before: two machines working separately, with you moving context back and forth. Now: one sentence, the peer’s agent runs it, and the result comes back on its own.

5 分钟上手

1. 每台机器装一遍

   dsh plugin add dsh-plugin-mesh复制

   desktop profile 要在 DSH 自带终端里跑；其它 profile 用普通终端即可。

2. 重启 DSH

   插件在启动时加载，装完必须重启一次。

3. 侧栏点「Mesh」，起个名字

   第一次会让你给这台机器起名（默认主机名）。别的机器就靠这个名字找你。两台在同一局域网，几秒内就会互相出现。

4. 派一个活，然后去看结果

   选一台设备 →「派发任务」，或者直接在会话里以 @机器名 开头说话。派出去只是「送达」；对端跑完会把结果派回来，出现在「任务」里。第一次往陌生设备派活时，对方会先弹一次「允许」。

Quick start (5 minutes)

1. Install on every machine

   dsh plugin add dsh-plugin-meshCopy

   The desktop profile needs DSH's own terminal; other profiles work from a normal one.

2. Restart DSH

   Plugins load at startup, so restart once.

3. Open “Mesh” in the sidebar and name this machine

   First run asks for a name (hostname by default). Peers find you by that name. On the same LAN they show up within seconds.

4. Dispatch one task, then read the result

   Pick a device → “Dispatch”, or start a chat message with @machine. Sending only means “delivered”; the peer dispatches the result back into “Tasks” when it is done. The first task to an unknown machine asks that side for approval.

它是怎么做到的 不关心可以跳过

• 自己找 —— 每 5 秒向局域网发一个心跳包，同时监听同一个地址。所以不用填 IP。
• 派活 —— 把任务发给对方，对方自动开一个 agent 会话去做，做完再派回来。
• 两条路 —— 局域网优先；不在同一网络时，走插件自带的用户态 Tailscale（自动下载，不用装客户端）。需要免费注册 Tailscale 并生成一个授权码。
• 会什么 —— 每台机器把自己装的运行时、内存、显卡报上来，派活之前就能看出它做不做得了。

How it works skip if you only want the outcome

• Discovery — every 5 seconds each machine sends a heartbeat to the LAN and listens on the same address. That is why you never type an IP.
• Dispatch — a task is sent to the peer, which opens an agent session automatically, does the work, and dispatches the result back.
• Two channels — LAN first; across networks it falls back to a bundled userspace Tailscale node, downloaded automatically. No client to install. Needs a free Tailscale account and an auth key.
• Capabilities — each machine reports its runtimes, memory and GPU, so you can tell before dispatching whether it can do the job.

常见问题

• 看不到对方 —— 依次确认：① 两台在同一局域网？ ② 对端也装了、也重启了？ ③ 防火墙放行了 TCP 45917 和 UDP 45892？ 还不出现就点「局域网探测」—— 只要端口通，扫描就能发现，不依赖组播。
• 结果在哪 —— 在「任务」里。派发的返回只代表对端收下了，不代表跑完了；跑完的结果由对端派回来。
• 第一次派活，对方没反应 —— 默认会先问那台机器一次「允许」。点过之后同一台设备不再问；也可以在「连接 → 配对码」里改成两端同码，彻底关掉这个确认。
• Android 老掉线 —— 是系统省电在杀后台，不是插件的问题。把 DSH 加进电池优化白名单。
• 安全 —— 陌生设备第一次派活默认要本机确认；允许过的设备记在本地。在咖啡厅、宿舍这类网络，再打开「配对码」：两端用同一个码。所有数据都在本机，没有账号、没有云端。

Troubleshooting

• No peers — check in order: same LAN? peer also installed and restarted? firewall allows TCP 45917 and UDP 45892? Still nothing: use “Scan subnet” — if the port is reachable, the scan finds it without multicast.
• Where is the result? — In “Tasks”. A successful dispatch only means delivered; the peer dispatches the result back when it finishes.
• First dispatch to a new machine does nothing — By default that machine asks its owner once for “Allow”. After that it stops asking; or turn on pairing codes on both sides to skip the prompt entirely.
• Android keeps dropping — the OS is killing background apps, not a plugin bug. Add DSH to the battery whitelist.
• Security — a first task from an unknown machine needs local approval; approved machines are remembered locally. On café/dorm networks also turn on pairing codes. All data stays local: no account, no cloud.