V2EX / 2026-10-29

[分享创造] 搞了个 DSH 插件，把多个会话平铺在一屏，终于不用切来切去了

痛点最近一直在使用 dsh,经常同时跑多个会话（多个工作需求、bug 定位修复，再加上几个自己自娱自乐的小项目）。遇到的一个痛点就是多个项目需要来回切换：看完程度、看有没有卡在权限审批/方案决策、看有没有跑偏。经常和 A 聊着聊着就忘了 B 和 C, 回头一看 B 、C 卡在审批上，白白浪费了时间。而且切来切去，自己脑子里的上下文先乱了，还得往回翻翻聊天才能想起来之前在干啥。我现在觉得效率的瓶颈更多在于人本身的接受/处理信息的速度。 # dsh-mixer 所以我 vibe 了一个插件，解决方案简单粗暴：所有会话平铺在一屏插件叫 dsh-mixer< https://github.com/dtdths/dsh-mixer >，装完后右上角多个「调音台」按钮。装法一行（需要 DSH 0.2.1 以上的 Web 端）： ```bash dsh plugin --profile web add github:dtdths/dsh-mixer#v1.6.1 ``` 使用方法：点右上角「调音台」按钮或者直接敲 `/mixer` 即可切换多栏会话平铺视图。再点击右上角

Read original source

Source page screenshot: [分享创造] 搞了个 DSH 插件，把多个会话平铺在一屏，终于不用切来切去了 — Source page screenshot · www.v2ex.com2026-11-06 UTC

Source record

Source: V2EX
Published: 2026-10-29 13:11:14 UTC
First discovered: 2026-10-29 15:45:21.156Z
Last collected: 2026-10-29 15:45:21.156Z
Author: dtdths1
Topic: Developer tools
Classification: Open-source projects & tools
Evidence level: E1 · source record; conclusions unverified

Research analysis

Rule-based research guidance derived from the source record. Audience and commercial demand require validation.

Project record

Source account: # 痛点最近一直在使用 dsh,经常同时跑多个会话（多个工作需求、bug 定位修复，再加上几个自己自娱自乐的小项目）。遇到的一个痛点就是多个项目需要来回切换：看完程度、看有没有卡在权限审批/方案决策、看有没有跑偏。经常和 A 聊着聊着就忘了 B 和 C, 回头一看 B 、C 卡在审批上，白白浪费了时间。而且切来切去，自己脑子里的上下文先乱了，还得往回翻翻聊天才能想起来之前在干啥。我现在觉得效率的瓶颈更多在于人本身的接受/处理信息的速度。 # dsh-mixer 所以我 vibe 了一个插件，解决方案简单粗暴：所有会话平铺在一屏插件叫 dsh-mixer< https://github.com/dtdths/dsh-mixer >，装完后右上角多个「调音台」按钮。装法一行（需要 DSH 0.2.1 以上的 Web 端）： ```bash dsh plugin --profile web add github:dtdths/dsh-mixer#v1.6.1 ``` 使用方法：点右上角「调音台」按钮或者直接敲 `/mixer` 即可切换多栏会话平铺视图。再点击右上角

Observed adoption & comparisons

Recent records to compare: “astral-sh/ruff” (GitHub Trending, Nov 6, 2026); “microsoft/vscode” (GitHub Trending, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.