Repository navigation
Releases
Releases · peiyucn/dsh-launcher-panel
v0.4.6
English
- The DeepSeek API Status card lays the API entries out as pills in a left column and keeps a single
Last checkedblock in a right column, separated by a divider; the label and time are on separate lines. The card reports one time for the whole card instead of one per model row. - The account balance stays on a single line, so a long balance or error message no longer wraps character by character.
- No other user-perceivable changes: internal tooling and lint moved to the shared baseline.
中文
- DeepSeek API Status 卡片改为左右两列:左侧 API 以胶囊排列,右侧单列显示
Last checked标签与时间(分两行),中间用竖线分隔;整卡只显示一个检查时间,不再在每个模型行重复。 - 账户余额保持单行显示,长余额或错误信息不再逐字换行。
- 无其他用户可感知的变化:仅内部工具链与 lint 调整。
v0.4.5
English
- The DeepSeek API Status card monitors the official chat service again: a
DeepSeek Chatrow shows its status and last-read time, incidents that affect it are listed with the model incidents, and clicking the row opens chat.deepseek.com in the configured browser. The chat section's file-upload and search services stay out of the card.
中文
- DeepSeek API Status 卡片重新纳入官方聊天服务监控:
DeepSeek Chat行显示其状态与最后读取时间,相关告警与模型告警一并列出;点击该行用当前浏览器设置打开 chat.deepseek.com。聊天分区下的上传与搜索服务仍不在卡片内。
v0.4.4
English
- The DeepSeek API Status card now monitors only the model APIs: the search/fetch API rows and the chat-service section (with its
Open chatlink) are gone, and only incidents that affect a model API are reported. Each model gets its own row with the time its status was last read. - The delete button is disabled while a launcher-managed instance is running, matching the edit button; detected read-only instances can still be removed while their process runs.
中文
- DeepSeek API Status 卡片现在只监控模型 API:移除 search / fetch(其他 API)与 chat-service 分区(含
Open chat入口),告警只显示影响模型 API 的条目;每个模型独立一行,并显示该状态最后一次读取时间。 - launcher 托管的实例运行中禁用删除按钮,与编辑按钮一致;探测接管的只读实例仍可在进程运行时删除。
v0.4.3
English
- Fixed: a detected (read-only) instance can now be removed from the panel even while its dsh process is running; removal only drops the launcher's record and never stops or touches that process (previously it asked the user to stop an instance the launcher does not manage).
中文
- 修复:探测接管的只读实例,即使对应的 dsh 进程正在运行,也可以直接从面板删除;删除只移除 launcher 的记录,不会停止或影响该 dsh 进程(此前会要求先停止,但 launcher 并不管理它)。
v0.4.2
English
- dsh 0.2.2 support: the source checkout is pinned to the latest official release tag (fresh clones check it out automatically; an old launcher-managed checkout switches to the tag automatically when no instance is running), update checks now compare HEAD against the tag, and the version label no longer shows -N-gsha.
- Since dsh 0.2.2 the launcher verifies Node >= 24.9 before starting and stops with an upgrade hint when it is older (earlier dsh lines still allow Node 22); the README requirement is updated accordingly.
中文
- 适配 dsh 0.2.2:source 模式固定到最新官方 release tag(fresh clone 自动 checkout;托管的旧 checkout 在无实例运行时自动切 tag),更新检查改为 HEAD 是否正好在 tag 上、版本显示不再带 -N-gsha。
- dsh 0.2.2 起启动前校验 Node >= 24.9,过旧时提示升级并停止启动(更早版本线仍允许 Node 22);README 环境要求已同步为 24.9+。
v0.4.1
English
- The DeepSeek API Status section is expanded by default when the panel opens; it can still be collapsed with the section header.
- No other user-perceivable changes: internal refactor of the detected-instance support. Process listing and dsh command-line matching are shared in one module, the launch token and package/version of a detected dsh are resolved in a single process scan, and the read-only state is extracted from the runtime state machine. Behaviour and settings are unchanged.
中文
- DeepSeek API Status 区在面板打开时默认展开;仍可用区标题折叠。
- 其余无用户可感知的变化:探测实例功能的内部重构。进程列表与 dsh 命令行识别收敛到共享模块;探测实例的启动 token 与 package/版本改为一次进程扫描解析;只读状态从运行状态机中抽出。行为与配置均不变。
v0.4.0
English
- Detected instances: the
+menu and theDetect Running dshcommand scan once (on demand) for dsh web servers on this machine that the launcher did not start, such as a systemd, docker or manually started install. Selected servers become read-only instances: the launcher observes them and opens their Web UI in a new tab, and never starts, stops, restarts or updates them. The launch token is resolved automatically from the process (systemd journal, docker logs or a redirected log file), with no configuration; when it cannot be resolved the tab still shows the running state and explains why. Detected instances can be renamed and deleted; the panel shows their own package path and dsh version. In a Remote-SSH window the Web UI opens through VS Code's port forwarding, so the tab reaches the remote host rather than the local machine. Copy takeover info opens a Markdown preview of a token-free briefing (and copies the same text) for handing the instance to an agent that converts it into a launcher-managed instance. - dsh is now detached from the VS Code extension host: reloading or closing the window no longer stops a running server. Use Stop in the panel or the command palette to end it.
- New
dsh.packageImportMethodsetting (defaultcopy): pnpm installs dsh's files as independent copies instead of hardlinks. On machines where security software filters file access, hardlinked files can be much slower to open, which delays each Stop→Start; the copy layout avoids that per-open overhead at the cost of a little extra disk space. Changing the setting takes effect on the next Start: the same version is reinstalled in place with the new method (keep the terminal open; skipped while another instance is running); if it fails, deleting the install folder and starting again recovers with a clean install. The Reinstall dsh (apply install method) command forces it immediately. Upgrading from 0.3.x triggers this one-time conversion on the first Start (the old install was hardlinked, the new default is copy): this is expected and normal — keep the terminal task open until it finishes, then Start continues as usual.
中文
- 探测实例:
+菜单与Detect Running dsh命令会在用户点击时扫描一次本机非 launcher 启动的 dsh Web 服务(systemd、docker 或手动启动的安装)。选中的服务会成为只读实例:launcher 只观察并在新标签页打开其 Web UI,不会启动、停止、重启或更新它。启动 token 自动从进程读取(systemd journal、docker logs 或被重定向的日志文件),无需任何配置;读不到时实例仍显示运行状态并说明原因。探测实例可改名、可删除,面板会显示它自己的 package 路径与 dsh 版本。在 Remote-SSH 窗口中,Web UI 通过 VS Code 端口转发打开,标签页访问的是远端主机而不是本机。Copy takeover info 会先打开一段不含 token 的信息卡 Markdown 预览(并同时复制),交给 agent 把实例转成 launcher 托管。 - dsh 与 VS Code 扩展宿主分离:重载或关闭窗口不再带走正在运行的 dsh 服务;需要停止时用面板或命令面板的 Stop。
- 新增
dsh.packageImportMethod设置(默认copy):pnpm 以独立复制方式而非硬链接安装 dsh 文件。在有安全软件过滤文件访问的机器上,硬链接文件打开可能明显更慢,从而拖慢每次 Stop→Start;copy 布局避免这种每次打开的开销,代价是多占一点磁盘。改设置会在下一次 Start 时生效:同一版本会在原目录重装为新方式(终端跑完前不要关闭;有其他实例在运行时跳过);失败时删除安装目录后重新 Start 即可干净恢复。Reinstall dsh (apply install method) 命令可立即强制重装。从 0.3.x 升级的用户会在第一次 Start 时遇到这次一次性转换(旧安装是硬链接、新默认是 copy):这是正常现象,可能需要一点时间,请在终端任务结束前不要关闭,完成后会照常启动。
v0.3.7
English
- Start in pkg mode is faster: the launcher runs the installed dsh CLI directly instead of going through
pnpm exec, and an already-installed start no longer probes pnpm or runspnpm --version. In testing the removed packaging layer cost 1.8–2.3 seconds per start and up to about 7 seconds on a full boot. - The first readiness probe now runs immediately, so a server that is already answering is detected without waiting an extra poll interval (up to 0.5 seconds per start).
- Source mode no longer runs a second
git describeduring the same start. - Each Start records per-stage timings in the launcher log (
start: preflight/prepare/profile/server spawned/settled), so a slow start can be attributed to the launcher, the profile, or dsh itself.
中文
- pkg 模式 Start 变快:直接运行已安装的 dsh CLI,不再经
pnpm exec转发;已安装情况下的启动也不再探测 pnpm 或执行pnpm --version。实测去掉的包装层每次启动约 1.8–2.3 秒,完整启动最多约 7 秒。 - 首次就绪探测改为立即执行,已经能应答的服务器不再多等一个轮询间隔(每次启动最多省 0.5 秒)。
- source 模式同一次启动不再重复执行
git describe。 - 每次 Start 会把各阶段耗时写入 launcher 日志(
start: preflight/prepare/profile/server spawned/settled),可据此区分慢在扩展前置、profile 还是 dsh 自身。
v0.3.6
English
- The DeepSeek status section is now titled DeepSeek API Status. Its status-page link moved into the section header as an arrow icon right after the title; the account row no longer carries it.
- Expanding the card now shows the official chat-service section:
chat-service,file-upload-serviceandsearch-serviceeach report their live status, and chat-service incidents appear with the other warnings. - A new Open chat button (chat icon) opens
chat.deepseek.comin the configured browser, putting the free DeepSeek chat one click away from the panel. - Development dependencies (minimatch, qs, glob) were upgraded to patched versions. They are not part of the packaged extension, so there is no user-perceivable change.
中文
- DeepSeek 状态区改名 DeepSeek API Status;状态页链接移到标题行,改为紧接标题的小箭头图标,账户行不再保留。
- 卡片展开后新增官方 chat-service 分区:
chat-service、file-upload-service、search-service三个服务各自显示状态;chat-service 相关告警会出现在下面的告警行。 - 新增 Open chat 按钮(聊天图标),一键在当前浏览器设置下打开
chat.deepseek.com,免费聊天入口就在面板里。 - 开发依赖(minimatch、qs、glob)升级到修复版本;它们不进扩展产物,无用户可感知的变化。
v0.3.5
English
- Stop no longer asks for confirmation. A server the launcher started but does not track in this window (for example after a VS Code reload) is now identified by its command line and stopped directly — this also fixes cases where confirming the old dialog left the server running. A port held by a process that cannot be identified as the instance's DSH server is not killed: the reason is reported in the panel and activity log instead.
- Stop reacts immediately: the button and status line show "Stopping…" on click, and the instance state switches to stopping before the process scan.
- The panel console's startup output now contains only the current launch; with
dsh.clearServerLogOnStartoff, earlier runs no longer leak into it. - Periodic plugin chatter (model listings) is filtered from the console and the launch token is masked; the complete text stays in the instance's
server.log.
中文
- 停止实例不再弹确认框。扩展重载后接管、或本窗口未跟踪的 DSH 服务器,改为按进程命令行识别后直接停止;这也修复了旧确认框「点了也停不下来」的情况。端口被无法识别为该实例 DSH 服务器的进程占用时不杀进程,只在面板与活动流里说明原因。
- Stop 点击立即有反馈:按钮与状态行马上显示
Stopping…,实例状态在进程识别之前就切到 stopping。 - 面板 Console 的启动输出只包含本次启动:即使关闭
dsh.clearServerLogOnStart,旧运行也不会再混进来。 - 周期性插件日志(model listing)从 Console 过滤,launch token 打码;完整原文仍在该实例的
server.log。