dsh-matlab-runner

Matlab Runner

DeepSeek Harness 侧边栏中的 MATLAB：类似 VS Code 的 .m 编辑器，配备持久化 MATLAB 会话（图形确实可以打开）、支持额外挂载文件夹的文件树、实时工作区变量、.mlx 预览，以及面向代理的 matlab_run 工具。

目标 Profile

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:seally-web/dsh-matlab-runner#5212ddbe3487249a83ea95ea4f0e65789171d5e8

兼容性与来源证明

Matlab Runner 以 dsh-matlab-runner 发布，当前版本为 0.2.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围: *
运行环境: web
发布来源: github
Registry 更新时间: 2026/10/30

版本

0.2.2stable

2026/10/30

README

dsh-matlab-runner

A DeepSeek Harness plugin that puts a VS Code–shaped MATLAB panel in the right sidebar: edit .m code, press ⌘/Ctrl+Enter, watch the console, open figures inline, keep a warm MATLAB session between runs, browse several folders like MATLAB's add-to-path list, and inspect/assign workspace variables.

dsh-matlab-runner is a UI plugin: the host half spawns MATLAB with the system user's permissions (not the agent's sandbox) and the browser half gives you an editor + runner + workspace inspector. Unlike the MCP-based MATLAB plugins, it is not an agent tool wrapper — the agent does get a matlab_run tool, but the panel is the product.

Two halves in one package:

Half	File	What it does
Host	`lib/index.js`, `lib/runner.js`	Owns the persistent MATLAB session and the run registry, serves `/matlab/api/*`, and registers the `matlab_run` agent tool.
Browser	`lib/client.js`	A page-type sidebar tab (editor, gutter, script picker, Run/Stop/Save, live console, figure previews, settings) plus a guide card and the `matlab-runner.open` shortcut.

The panel

A real run: file tree + variables on the left, editor in the middle, live console below, exported figures as thumbnails. Dividers resize the tree, the variables pane and the console; settings are one click away.

Settings	Narrow sidebar
Settings	Narrow

Two run modes

session (default) — one long-lived matlab -nodesktop -nosplash process fed through stdin. After the first boot (≈6–9 s) a run costs ~10–30 ms, the prompt keeps your variables between runs, and figure windows really open on the desktop while the panel also shows the exported PNG. Output is streamed into the console while the script is still running.
batch — matlab -batch per run, headless, exits with the script (15–20 s per call, no windows). Kept for CI-ish, leave-nothing-behind work.

The session is shared between the sidebar and the agent tool, so what the model runs and what you type land in the same MATLAB workspace.

Why this runs when the agent's shell cannot

MATLAB needs to write ~/Library/Application Support/MathWorks before it will start. A sandboxed shell (workspace-write) makes matlab -batch exit 1 with an empty console, and a PTY tab owned by the agent is subject to the same sandbox. The host half spawns MATLAB with node:child_process from the host process, i.e. with the system user's permissions, independently of the agent's sandbox mode — so this panel runs MATLAB without switching the session to Full access.

Install

From npm (once published):

dsh plugin --profile web add dsh-matlab-runner

For the desktop app, whose profile is owned by the Electron application, use the bundled script — it copies the payload into the profile, wires the dependency and the dsh.profile.bundles row, seeds the config, and re-composes the plugin:

node bin/install-local.sh        # or: plugins/dsh-matlab-runner/bin/install-local.sh

The official desktop app owns its profile, so the script copies the payload into ~/.dsh/profiles/desktop/node_modules/dsh-matlab-runner, adds the dependency and the dsh.profile.bundles row, seeds the config, and re-composes the plugin's Loader entry.

About that last step: the app watches ~/.dsh/profiles/desktop/package.json, so dropping the bundle row and putting it back reloads the plugin from disk — no app restart, no lost session. bin/reload-host.sh does exactly that:

plugins/dsh-matlab-runner/bin/reload-host.sh   # host half picked up new files

Then reload the page (⌘/Ctrl+R) so the browser half updates too. A full app restart is only needed if the tab still shows the old panel.

Open it

Right sidebar → the add control (+) → the MATLAB 运行器 / MATLAB runner card. After the first visit the tab is in the strip; ⌘/Ctrl+Shift+M opens it from anywhere (web builds: ⌘/Ctrl+Shift+Alt+M).

What the panel does

File tree (⌸ 文件) — browse workdir from the panel, expand folders lazily, click any text file to open it in the editor (↑ 上一级 walks up, 刷新 re-reads). Only files with a text extension are editable; anything else reports binary.
Editor with a line-number gutter, MATLAB syntax highlighting (keywords, strings, numbers, comments), no autocorrect, Tab = two spaces.
Run (⌘/Ctrl+Enter) writes the buffer to <workdir>/.dsh-matlab-runner/<stem>.m and runs it in the persistent session.
Script picker — every .m in scriptDir plus every unsaved draft. Picking one loads it into the editor. ＋ New starts a blank buffer, and every buffer is remembered (per file path, plus each draft) so switching files or tabs never throws typed code away.
Multiple folders — the tree header has a folder picker plus a + button. + mounts any absolute path (~ works) as an extra tree root, exactly like MATLAB's "add to path" list; mounts are persisted in matlab-runner.json as extraRoots and can be removed again from the same row. Mounted folders are browsable and editable, but a run's working directory still follows the workspace (relative paths stay anchored to the script being run).
Variable editor — double-click any row in the variables panel to open the value; edit the literal and 写回工作区 / Write back assigns it with evalin('base', '<name> = <literal>;'), so it really replaces the MATLAB variable (the panel refreshes right after). Numerics are shown with mat2str, anything else through evalc('disp(x)').
Stop / ■ aborts the current script (in session mode this restarts the MATLAB session; the next run boots it again).
Save writes a real script to <scriptDir>/<name>.m.
Console streams stdout/stderr live, then shows exit code, elapsed time, and the script path. Errors print getReport(e,'extended'), so line numbers survive.
Autosave — after a run that exits cleanly the buffer is written back to disk: opened files go to their own path, drafts are saved as a new script under scriptDir. Turn it off with the autoSave setting or the Settings checkbox.
Drag the dividers — one between the file tree and the editor (width), one between editor and console (height); both are remembered per browser.

Interface

The panel follows the VS Code / MATLAB layout conventions:

Area	What it holds
Toolbar	Three groups: run (▶ Run / ■ Stop / Save), files (script picker + New), views (file tree / variables). The session badge and the settings gear sit on the right.
Breadcrumb	The folder the panel currently points at, clickable per segment, plus the edit target on the right.
Left column	File tree on top, MATLAB workspace variables underneath (name / value / class / size), with a drag bar between them and a vertical drag bar against the editor.
Editor	Gutter, syntax highlighting, splitter above the console — drag it to resize.
Console	Header strip, streaming output, figure thumbnails, and a status bar with phase, exit code, elapsed time and the script path.
Settings	Three labelled sections — run, workspace, MATLAB — as a label/control grid, with the current detection source, "follow this workspace", "pin to this path", Save and Restart session.

Panel toggles (tree / variables) are remembered per browser. node bin/preview-ui.mjs renders the two views to /tmp/mrun-*.html for a quick headless look:

node bin/preview-ui.mjs
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new \
  --screenshot=/tmp/panel.png --window-size=980,760 file:///tmp/mrun-panel.html

Saving, drafts and buffers

Buffer	What Save does	Where it lives
An opened file (picked from the tree or the script picker)	Overwrites that file in place — same as the editor's ⌘S. Auto-save (after a clean run) does the same.	the file itself
A draft (`＋ new`, name without a path)	Saves a copy to `<scriptDir>/<name>.m` and switches the buffer to that file.	`<scriptDir>` (default `<workspace>/matlab`)
Unsaved edits of either kind	Kept in browser `localStorage` under `dsh.matlab-runner.buffers`, so switching files or reloading never loses them.	browser storage
The script MATLAB actually executes	A draft runs from a temporary copy in `<workspace>/.dsh-matlab-runner/`; an opened file runs in place, so relative paths resolve next to it.	workspace

Config

~/.dsh/matlab-runner.json ($DSH_HOME/matlab-runner.json when set), created on first boot with the paths this machine actually uses:

{
  "mode": "session",
  "warmFigures": false,
  "autoSave": true,
  "autoDetect": true,
  "matlabPath": "/path/to/MATLAB/bin/matlab",
  "sessionArgs": ["-nodesktop", "-nosplash"],
  "extraArgs": ["-nodisplay", "-nosplash"],
  "workdir": "~/your-project",
  "scriptDir": "~/your-project/matlab",
  "timeoutMs": 600000,
  "env": {}
}

mode — session (persistent, fast, figures open) or batch (one process per run, headless).
warmFigures — true initializes the graphics/Java stack during boot, so the first figure costs ~2 s instead of ~13 s; the first run pays that cost up front instead.
autoSave — true (default): a successful run writes the buffer back to the open file (or saves a draft as scriptDir/<name>.m).
autoDetect — true (default): workdir follows the folder the DSH session has open and scriptDir becomes <workspace>/matlab, so switching projects needs no config edit. false pins the two paths below.
matlabPath — the launcher binary (an app bundle's bin/matlab, not the Contents/MacOS payload).
sessionArgs — flags after matlabPath for the persistent process.
extraArgs — flags before -batch in batch mode.
workdir — the session's working directory, and the root scratch scripts are written under. With autoDetect on this is derived, not fixed.
scriptDir — where Save puts .m files and where the picker looks (<workspace>/matlab in auto mode).
timeoutMs — hard cap per run; Stop is the manual version.
env — extra environment variables for MATLAB.

Everything except env is editable in the panel's Settings pane.

Which folder does a script run in?

A buffer that maps to a real file runs that file, so MATLAB's working directory is the file's own folder and readmatrix('data.xlsx') resolves next to the script (same as the editor's Run button). Drafts still run from the scratch copy under <workspace>/.dsh-matlab-runner/, and when MATLAB cannot find a relative path the console shows the base folder:

相对路径以脚本所在目录为基准: /…/W07_quiz（数据文件放这里，或用绝对路径）

Which folder does it use?

The tab sends its session's workspace root with every API call (?cwd=), so:

Session folder wins — the panel always works on what you have open.
Otherwise the first folder in ctx.workspaceRegistry, then the host process cwd (this is what the agent tool sees when no panel is talking).
A report older than 2 minutes is treated as stale, so matlab_run never inherits a folder you closed long ago.
autoDetect: false skips all of the above and uses workdir/scriptDir.

Settings shows the detected root and its source, with 跟随当前工作区 and 固定为当前路径 buttons. Path rejections name the folder you are on, e.g. path outside the configured roots: /etc · 当前工作区: /tmp（面板 → 设置 → 自动检测 / 使用当前工作区）.

Agent side

matlab_run({ code | file, name? }) runs one script through the same registry and returns its console text, so the model can iterate on MATLAB code, read the output, and see errors (the wrapper prints getReport(e,'extended')).

Tests

node plugins/dsh-matlab-runner/test/host-unit.mjs     # names, argv, config dialect, path containment, vars helper
node plugins/dsh-matlab-runner/test/client-smoke.mjs  # loader shell + registration order
node plugins/dsh-matlab-runner/test/client-render.mjs # renders the panel body once against stubs
node plugins/dsh-matlab-runner/test/client-tokenize.mjs # highlighter token split (transpose vs string, comments, numbers)
node plugins/dsh-matlab-runner/test/livemd.mjs        # .mlx parser, self-contained fixture
node plugins/dsh-matlab-runner/test/host-apply.mjs    # the whole apply(): routes, tool, tree, vars, session (~40 s)
node plugins/dsh-matlab-runner/test/session.mjs       # real MATLAB: boot, warm reuse, errors, figures, stop (~50 s)
node plugins/dsh-matlab-runner/test/host-run.mjs      # real MATLAB batch path (needs an unsandboxed shell)

bin/check.mjs is the live one: it talks to the running app over loopback (DSH_GUI_URL, default http://127.0.0.1:54501), prints the resolved config, runs a script, proves the session is reused on the next run, and fetches the exported figure through the artifact route. A pass proves the host half is live and MATLAB is reachable; only the page can prove the tab rendered.

The MATLAB tests fail under a sandboxed shell by design — they exercise the same spawn path the app uses, which only exists outside the sandbox.

Limits

First figure in a session costs ~13 s (Java/desktop initialization), then ~2 s. Turn on warmFigures to move that cost to boot.
Don't name a script after a MATLAB builtin (plot.m, mean.m, …): run resolves the script first and shadows the function, so plot.m fails with "不支持将脚本 plot 作为函数执行".
One session per host, shared by the panel and the agent tool; a long pause or an infinite loop blocks that session until Stop.
The variables panel lists base-workspace variables only, and it needs a running session (before the first run it says "session not started").
Windows is untested; sessionArgs/extraArgs and the launcher path would need adjusting.
Until the first successful run (or a manual Save) buffers live in localStorage only, so they survive tab switches and page reloads but not a different browser or a cleared profile.
Syntax highlighting is a tokeniser, not a parser: it does not fold blocks, and a % inside an unusual context can still be read as a comment.
.mlx is preview only — the panel renders what MATLAB saved, but cannot edit or run a live script (that needs the Live Editor engine). Section counts are a heuristic for live scripts imported from Word; the order of blocks is always the document order.
Stopping or restarting the session asks MATLAB to exit first, so no -nodesktop process is left behind. A long-running -nodesktop MATLAB does register with macOS under MATLAB's bundle id, which can make a Finder double-click look like a no-op (the windowless instance receives the activation). Fix: open -n -a /Applications/MATLAB_R2026a.app or quit the session; in VS Code set MATLAB.matlabConnectionTiming to onDemand.
The file tree is rooted at workdir; it does not follow the DSH workspace switcher or show git status.
MATLAB file names must start with a letter: a generated helper named _vars.m fails with "文本字符无效".

License

README

dsh-matlab-runner

Two halves in one package:

Half	File	What it does
Host	`lib/index.js`, `lib/runner.js`	Owns the persistent MATLAB session and the run registry, serves `/matlab/api/*`, and registers the `matlab_run` agent tool.
Browser	`lib/client.js`	A page-type sidebar tab (editor, gutter, script picker, Run/Stop/Save, live console, figure previews, settings) plus a guide card and the `matlab-runner.open` shortcut.

The panel

Settings	Narrow sidebar
Settings	Narrow

Two run modes

session (default) — one long-lived matlab -nodesktop -nosplash process fed through stdin. After the first boot (≈6–9 s) a run costs ~10–30 ms, the prompt keeps your variables between runs, and figure windows really open on the desktop while the panel also shows the exported PNG. Output is streamed into the console while the script is still running.
batch — matlab -batch per run, headless, exits with the script (15–20 s per call, no windows). Kept for CI-ish, leave-nothing-behind work.

The session is shared between the sidebar and the agent tool, so what the model runs and what you type land in the same MATLAB workspace.

Why this runs when the agent's shell cannot

Install

From npm (once published):

dsh plugin --profile web add dsh-matlab-runner

node bin/install-local.sh        # or: plugins/dsh-matlab-runner/bin/install-local.sh

plugins/dsh-matlab-runner/bin/reload-host.sh   # host half picked up new files

Then reload the page (⌘/Ctrl+R) so the browser half updates too. A full app restart is only needed if the tab still shows the old panel.

Open it

What the panel does

File tree (⌸ 文件) — browse workdir from the panel, expand folders lazily, click any text file to open it in the editor (↑ 上一级 walks up, 刷新 re-reads). Only files with a text extension are editable; anything else reports binary.
Editor with a line-number gutter, MATLAB syntax highlighting (keywords, strings, numbers, comments), no autocorrect, Tab = two spaces.
Run (⌘/Ctrl+Enter) writes the buffer to <workdir>/.dsh-matlab-runner/<stem>.m and runs it in the persistent session.
Script picker — every .m in scriptDir plus every unsaved draft. Picking one loads it into the editor. ＋ New starts a blank buffer, and every buffer is remembered (per file path, plus each draft) so switching files or tabs never throws typed code away.
Multiple folders — the tree header has a folder picker plus a + button. + mounts any absolute path (~ works) as an extra tree root, exactly like MATLAB's "add to path" list; mounts are persisted in matlab-runner.json as extraRoots and can be removed again from the same row. Mounted folders are browsable and editable, but a run's working directory still follows the workspace (relative paths stay anchored to the script being run).
Variable editor — double-click any row in the variables panel to open the value; edit the literal and 写回工作区 / Write back assigns it with evalin('base', '<name> = <literal>;'), so it really replaces the MATLAB variable (the panel refreshes right after). Numerics are shown with mat2str, anything else through evalc('disp(x)').
Stop / ■ aborts the current script (in session mode this restarts the MATLAB session; the next run boots it again).
Save writes a real script to <scriptDir>/<name>.m.
Console streams stdout/stderr live, then shows exit code, elapsed time, and the script path. Errors print getReport(e,'extended'), so line numbers survive.
Autosave — after a run that exits cleanly the buffer is written back to disk: opened files go to their own path, drafts are saved as a new script under scriptDir. Turn it off with the autoSave setting or the Settings checkbox.
Drag the dividers — one between the file tree and the editor (width), one between editor and console (height); both are remembered per browser.

Interface

The panel follows the VS Code / MATLAB layout conventions:

Area	What it holds
Toolbar	Three groups: run (▶ Run / ■ Stop / Save), files (script picker + New), views (file tree / variables). The session badge and the settings gear sit on the right.
Breadcrumb	The folder the panel currently points at, clickable per segment, plus the edit target on the right.
Left column	File tree on top, MATLAB workspace variables underneath (name / value / class / size), with a drag bar between them and a vertical drag bar against the editor.
Editor	Gutter, syntax highlighting, splitter above the console — drag it to resize.
Console	Header strip, streaming output, figure thumbnails, and a status bar with phase, exit code, elapsed time and the script path.
Settings	Three labelled sections — run, workspace, MATLAB — as a label/control grid, with the current detection source, "follow this workspace", "pin to this path", Save and Restart session.

Panel toggles (tree / variables) are remembered per browser. node bin/preview-ui.mjs renders the two views to /tmp/mrun-*.html for a quick headless look:

node bin/preview-ui.mjs
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new \
  --screenshot=/tmp/panel.png --window-size=980,760 file:///tmp/mrun-panel.html

Saving, drafts and buffers

Buffer	What Save does	Where it lives
An opened file (picked from the tree or the script picker)	Overwrites that file in place — same as the editor's ⌘S. Auto-save (after a clean run) does the same.	the file itself
A draft (`＋ new`, name without a path)	Saves a copy to `<scriptDir>/<name>.m` and switches the buffer to that file.	`<scriptDir>` (default `<workspace>/matlab`)
Unsaved edits of either kind	Kept in browser `localStorage` under `dsh.matlab-runner.buffers`, so switching files or reloading never loses them.	browser storage
The script MATLAB actually executes	A draft runs from a temporary copy in `<workspace>/.dsh-matlab-runner/`; an opened file runs in place, so relative paths resolve next to it.	workspace

Config

~/.dsh/matlab-runner.json ($DSH_HOME/matlab-runner.json when set), created on first boot with the paths this machine actually uses:

{
  "mode": "session",
  "warmFigures": false,
  "autoSave": true,
  "autoDetect": true,
  "matlabPath": "/path/to/MATLAB/bin/matlab",
  "sessionArgs": ["-nodesktop", "-nosplash"],
  "extraArgs": ["-nodisplay", "-nosplash"],
  "workdir": "~/your-project",
  "scriptDir": "~/your-project/matlab",
  "timeoutMs": 600000,
  "env": {}
}

mode — session (persistent, fast, figures open) or batch (one process per run, headless).
warmFigures — true initializes the graphics/Java stack during boot, so the first figure costs ~2 s instead of ~13 s; the first run pays that cost up front instead.
autoSave — true (default): a successful run writes the buffer back to the open file (or saves a draft as scriptDir/<name>.m).
autoDetect — true (default): workdir follows the folder the DSH session has open and scriptDir becomes <workspace>/matlab, so switching projects needs no config edit. false pins the two paths below.
matlabPath — the launcher binary (an app bundle's bin/matlab, not the Contents/MacOS payload).
sessionArgs — flags after matlabPath for the persistent process.
extraArgs — flags before -batch in batch mode.
workdir — the session's working directory, and the root scratch scripts are written under. With autoDetect on this is derived, not fixed.
scriptDir — where Save puts .m files and where the picker looks (<workspace>/matlab in auto mode).
timeoutMs — hard cap per run; Stop is the manual version.
env — extra environment variables for MATLAB.

Everything except env is editable in the panel's Settings pane.

Which folder does a script run in?

相对路径以脚本所在目录为基准: /…/W07_quiz（数据文件放这里，或用绝对路径）

Which folder does it use?

The tab sends its session's workspace root with every API call (?cwd=), so:

Session folder wins — the panel always works on what you have open.
Otherwise the first folder in ctx.workspaceRegistry, then the host process cwd (this is what the agent tool sees when no panel is talking).
A report older than 2 minutes is treated as stale, so matlab_run never inherits a folder you closed long ago.
autoDetect: false skips all of the above and uses workdir/scriptDir.

Agent side

Tests

node plugins/dsh-matlab-runner/test/host-unit.mjs     # names, argv, config dialect, path containment, vars helper
node plugins/dsh-matlab-runner/test/client-smoke.mjs  # loader shell + registration order
node plugins/dsh-matlab-runner/test/client-render.mjs # renders the panel body once against stubs
node plugins/dsh-matlab-runner/test/client-tokenize.mjs # highlighter token split (transpose vs string, comments, numbers)
node plugins/dsh-matlab-runner/test/livemd.mjs        # .mlx parser, self-contained fixture
node plugins/dsh-matlab-runner/test/host-apply.mjs    # the whole apply(): routes, tool, tree, vars, session (~40 s)
node plugins/dsh-matlab-runner/test/session.mjs       # real MATLAB: boot, warm reuse, errors, figures, stop (~50 s)
node plugins/dsh-matlab-runner/test/host-run.mjs      # real MATLAB batch path (needs an unsandboxed shell)

The MATLAB tests fail under a sandboxed shell by design — they exercise the same spawn path the app uses, which only exists outside the sandbox.

Limits

First figure in a session costs ~13 s (Java/desktop initialization), then ~2 s. Turn on warmFigures to move that cost to boot.
Don't name a script after a MATLAB builtin (plot.m, mean.m, …): run resolves the script first and shadows the function, so plot.m fails with "不支持将脚本 plot 作为函数执行".
One session per host, shared by the panel and the agent tool; a long pause or an infinite loop blocks that session until Stop.
The variables panel lists base-workspace variables only, and it needs a running session (before the first run it says "session not started").
Windows is untested; sessionArgs/extraArgs and the launcher path would need adjusting.
Until the first successful run (or a manual Save) buffers live in localStorage only, so they survive tab switches and page reloads but not a different browser or a cleared profile.
Syntax highlighting is a tokeniser, not a parser: it does not fold blocks, and a % inside an unusual context can still be read as a comment.
.mlx is preview only — the panel renders what MATLAB saved, but cannot edit or run a live script (that needs the Live Editor engine). Section counts are a heuristic for live scripts imported from Word; the order of blocks is always the document order.
Stopping or restarting the session asks MATLAB to exit first, so no -nodesktop process is left behind. A long-running -nodesktop MATLAB does register with macOS under MATLAB's bundle id, which can make a Finder double-click look like a no-op (the windowless instance receives the activation). Fix: open -n -a /Applications/MATLAB_R2026a.app or quit the session; in VS Code set MATLAB.matlabConnectionTiming to onDemand.
The file tree is rooted at workdir; it does not follow the DSH workspace switcher or show git status.
MATLAB file names must start with a letter: a generated helper named _vars.m fails with "文本字符无效".

Matlab Runner

兼容性与来源证明

版本

相关插件

Matlab Runner

README

dsh-matlab-runner

Two run modes

Why this runs when the agent's shell cannot

Install

Open it

What the panel does

Interface

Saving, drafts and buffers

Config

Which folder does a script run in?

Which folder does it use?

Agent side

Tests

Limits

License

兼容性与来源证明

版本

相关插件

相关插件

相关插件

README

dsh-matlab-runner

Two run modes

Why this runs when the agent's shell cannot

Install

Open it

What the panel does

Interface

Saving, drafts and buffers

Config

Which folder does a script run in?

Which folder does it use?

Agent side

Tests

Limits

License