dsh-triage-desk
Manifest validCollects GitHub review requests, merge-ready pull requests, failing checks, and issues in one inbox, and opens a coding agent or a new DSH chat with a prepared prompt.
Triage Desk
A DeepSeek Harness (DSH) plugin that answers one question every morning: what needs me right now? It turns GitHub activity into a single inbox panel: reviews waiting on you, your merge-ready PRs, threads that need an answer, failing CI, and new or assigned issues. Copy a scenario prompt or open it as a draft in DSH, a local agent or a named SSH host. The inbox reads GitHub through the signed-in local CLI.
简体中文 · Reference · Architecture · Changelog
What it shows
- Reviews shows whose turn it is on a PR. Awaiting my review lists direct or team requests for PRs you have yet to review. Awaiting my re-review offers a pass over changes and replies since your review when the author re-requests you (even on the same commit), pushes new commits, or replies to you. A pending team request follows the PR into re-review after new commits. Feedback on my PRs lists comments and requested changes on your PRs, including drafts. Open the PR from its title or use the agent button to draft a reply. Requested changes also link to the changed files.
- Ready to merge lists your mergeable PRs that have approval or need none. By default, checks must pass or be absent. A PR with failing checks appears under CI is failing. Once its checks pass, it enters Ready to merge on the next refresh if otherwise eligible.
- Needs your action: merge conflicts, assigned issues, and unanswered mentions.
- CI is failing: red checks on your PRs, on default branches you maintain, and on branches whose latest commit you authored in the last week.
- New in your repositories: unassigned issues from the last 30 days, kept out of the attention counter.
- Snooze: per row, per section, or a selection, until new activity, tomorrow, or next week.
- Launch scenarios: editable prompts for individual rows or groups. After you upgrade and restart the DSH host, saved scenarios for Needs your action also apply to Feedback on my PRs. You can edit either binding in Settings.
- Agent tool:
triage_deskgives a DSH agent the same snapshot and can open a terminal on request. - Sources and languages: personal repositories plus up to 10 organizations; the panel follows the DSH language (English or Chinese).
- Large organizations: organizations as big as
llvmload in a lighter mode instead of failing (details).
The count next to Triage is what needs you; hover or focus it to see what it leaves out.
Each feature is described in full in the reference.
Requirements
- DeepSeek Harness
0.2.2-rc.2or newer. - GitHub only: GitLab, Bitbucket, Gitea, and other code hosts are not supported.
- The GitHub CLI installed and signed in (
gh auth login). Private repositories need thereposcope thatgh auth loginnormally grants. Settings shows the connection and has a Sign in to GitHub button. - Optional, for typing prompts into agents other than Claude Code: Python 3 on macOS and Linux, Windows 10 version 1809 or later on Windows (see prompt delivery).
Install
Triage Desk is a DSH bundle: DSH installs it into a profile and loads it as a plugin. There is no build step.
From npm
dsh plugin --profile <profile> add dsh-triage-desk
<profile> is the profile you run: web for dsh web, desktop for the
Desktop app. Restart DSH, refresh the page, and open the Triage entry in the
sidebar. The first run auto-detects your organizations; the gear in the header
changes them. Plugin Manager can also install the package by name.
To update later, run the following and restart DSH:
dsh plugin --profile <profile> add dsh-triage-desk@latest
Removing the plugin (dsh plugin --profile <profile> remove dsh-triage-desk,
or Remove in Plugin Manager) keeps your saved settings in the profile, and
a reinstall picks them up again. To start from the defaults, see
uninstall and saved settings.
From a local checkout (development)
- Clone the repository.
- In DSH open Plugins → Add plugin and pick the repository directory, or run
dsh plugin --profile <profile> add ./dsh-triage-deskfrom its parent folder. - Open the Triage entry in the sidebar.
After editing the host half, quit and reopen DSH, then refresh the page; see local development for the reload rules.
Launching agents
Open the terminal button on a row or section. The Prompt field contains the configured template filled in for this task. First reviews, re-reviews and issues use their respective templates. Change reusable instructions in Settings → Agents → Prompt templates. You can edit the draft for this launch without changing its template. Choose the local computer or an SSH host, then an agent. Switching machines keeps your edits. Open delivers the draft without sending it. Copy prompt copies your edited text and the row's Copy link copies the URL. An inbox refresh keeps your open draft and its original items. Reopen the editor to use the updated list.
Choose Terminal in the Agent list to open a shell on This computer or the selected SSH host. A single-repository task opens in its working copy when available. The shell opens with an empty command line and preserves your clipboard. Switching back to an agent before opening restores your edited draft.
Opening the first-review group includes its visible first reviews, even in All. Re-reviews have their own action. Their group prompt gives the reason for each PR and directs the agent to read author replies even when the diff is empty. In Feedback on my PRs, use the terminal button on a row to draft a reply for one PR, or the button in the group heading to prepare replies for several PRs. The count follows your source filter and search, skips snoozed items and counts each PR once. Rows marked Optional review are excluded by default. When a PR has new commits since your review, another reviewer's approval must cover the current head for the re-review to be optional. To pick individual PRs, including optional ones, click Select, check the rows you want, then open that group's terminal button. Its count shows how many you picked in that group. If the prompt size limit drops any items, the draft and notification show how many fit. If even the first item exceeds the limit, the panel shows an error before opening a draft. Each terminal batch opens a fresh tab or window. If the included PRs all belong to one repository, the launcher looks for a matching working copy, locally or on the selected SSH server.
Once you send it, the review scenarios post one GitHub review of inline comments
tagged [P1]–[P3], and never approve. The fix and reply scenarios wait for your
OK before pushing or posting; triage only reports back. None of them add AI
attribution.
GitHub settings. Expand GitHub for the connection, organizations, personal repositories, polling interval and PR rules. A connected account starts collapsed and shows its login in the heading. If a connection check fails, the heading shows the error. Expand GitHub to retry. When sign-in is needed, GitHub starts expanded.
Run on. In Settings → Agents, below GitHub, choose This computer or an
SSH host. The same list is available when opening a draft. It includes saved
destinations and named hosts from ~/.ssh/config. Selecting a host checks its
installed agents. Use Scan again after installing an agent, or Retry if
the connection fails. Hosts requiring interactive SSH login also allow a manual
agent choice. Add SSH host… lets you enter an alias manually.
Triage Desk keeps the spelling and case of each alias. Rename saved host…
moves its agent preferences and repository folders to the new alias in Triage Desk.
If a scan finds no agents, you can still reset a saved default to Automatic.
Each machine has its own default agent. Viewing a host in Settings only changes which preferences you edit. Prompt templates are shared across machines. For a template with an existing local agent override, Use machine default clears it.
For a local repository with several working copies, open Launch environments,
select This computer, and expand Repository overrides. Add the repository
and the local folder to use. Choosing a Git working copy with Repository
empty fills in its GitHub name. Save one folder per repository. For example,
Acme/App and acme/app refer to the same repository. The collapsed section
shows the number of overrides.
Under Launch environments → Repository folders on, select a host and enter one
folder per line, such as ~/projects or /srv/git. Home paths resolve on the
server. Save the folders and use Find repositories to inspect its working copies.
At launch, Git remotes identify the working copy, including forks with an
upstream remote. When several copies match, choose one and optionally remember
it. When none match, the terminal asks for a folder and shows the path Enter
will accept. An unavailable agent prompts for recovery in the same session.
Opening an ordinary shell requires your choice.
A failed connection offers a retry in the same terminal with the same draft.
If you leave before the agent starts, the launcher tries to delete its private
staging file over SSH. If the server is unreachable or requires another
password prompt, the terminal prints the filename so you can remove it after
reconnecting. A force-closed launcher can also leave a staging file named
.triage-desk-<uuid>.sh in your remote home directory.
The local machine needs OpenSSH. The server needs a POSIX shell, a writable home
directory and Git for repository discovery. The probe and launcher read the PATH from your interactive shell. Claude Code uses its native
--prefill flag, which puts the prompt in its command-line arguments. On a
shared server, users who can inspect that process can read the draft. To keep
it out of the process list, open Claude yourself and use Copy prompt.
Other remote agents need Python 3 and bracketed paste support. If an agent
doesn’t accept the draft within two minutes, choose Copy prompt in the panel
and then paste into the remote agent. Time spent at a recognized folder-trust dialog is excluded.
Remote agents start with their own default permissions. You can use Copy prompt
with any agent, including in an SSH session you already have open.
Terminals. Settings → Launch environments → Open agents in offers Automatic or one of this platform's terminals; terminals that are not installed are shown disabled.
| Platform | Terminals | Automatic |
|---|---|---|
| macOS | Terminal, iTerm2, Ghostty | iTerm2 when installed, otherwise Terminal |
| Linux | GNOME Terminal, Konsole, Xfce Terminal, Ghostty, kitty, Alacritty, xterm | $TERMINAL, then the first installed emulator |
| Windows | Windows Terminal, PowerShell window | Windows Terminal when installed |
iTerm2, Ghostty (macOS), GNOME Terminal, Konsole, Xfce Terminal, and Windows Terminal open a fresh tab for each draft; the others open a window per launch. A saved terminal that is not installed falls back to Automatic. The toast reports this for both local and SSH launches.
Prompt delivery. Claude Code opens with the prompt as its native
--prefill draft. On Windows that needs Claude Code as an .exe: an npm
install (a .cmd shim) is handled like the other agents, because cmd.exe
would not pass the prompt intact. So is an .exe shim from Scoop, bun,
Chocolatey, Volta, mise or proto, which can start a .cmd
(prompt delivery). For every other agent,
Settings → Launch environments → Prompt delivery offers these options.
- Type into the agent (default, recommended): a small paste wrapper waits
until the agent's input box is ready, then pastes the prompt into it without
pressing Enter. Needs Python 3 on macOS (
xcode-select --install) and Linux, or Windows 10 1809 or later; without it, launches use the clipboard and Settings and the toast say how to fix it. For a local launch that times out, paste the prompt from the clipboard. - Copy to clipboard: the agent opens empty and you paste the prompt (⌘V on macOS, Ctrl+Shift+V in Linux terminals, Ctrl+V on Windows).
The toast names the agent and the terminal, for example Codex opened in Ghostty (/path): the prompt will appear in its input box, not sent — review it and press Enter.
Agents. By default a launch opens a new DSH chat with the prompt, and the
menu lists the coding agents installed on this machine: Claude Code, Codex,
opencode, Gemini CLI, Cursor Agent, Antigravity (agy), pi, Aider, Amp, Droid,
Goose, and Crush. Pick another default in Settings, or add your own command. A
command must contain {prompt} exactly once, unquoted, as its own argument or
right after a --flag=.
Local agents start in full access, as Orca's default does: each built-in command
carries the agent's own flag for skipping permission prompts, such as
codex --dangerously-bypass-approvals-and-sandbox or
agy --dangerously-skip-permissions. A step a scenario asks the agent to
confirm first, such as pushing, then rests on the agent following its prompt. To
get the permission prompts back, remove the flag from the agent's command in
Settings (flags per agent).
Details: terminal launcher reference.
Settings
The gear in the panel header opens Settings. A save usually applies to the
running plugin without restarting it, so the triage_desk tool stays
available while you save. The most used fields:
| Field | Default | Meaning |
|---|---|---|
orgs | [] | Organizations to scan (at most 10); empty auto-detects them |
includePersonal | true | Include your personal repositories |
refreshSeconds | 1200 | Auto-refresh interval, 15–3600 s |
requireGreenChecks | true | Turn off to allow otherwise eligible PRs with pending or failing checks in Ready to merge. PRs GitHub marks BLOCKED are excluded with either setting. |
defaultAgent | dsh | Default for This computer. Choose dsh for a new DSH chat or a local agent ID. Each SSH host has its own preference. |
defaultScenario | empty | Choose by task, or save an applicable row scenario ID |
sshServers | [] | SSH alias, preferred agent, optional alternatives and ordered remote folders (absolute or ~/…). An existing cwd is read as one folder. |
terminal | auto | Terminal for launches: auto or a terminal id |
promptDelivery | paste | paste (type into the agent) or clipboard |
All fields, including agents, scenarios, and clone search, are in the configuration reference.
Development
npm install # dev dependencies and the pre-commit hook
npm run check # lint, docs links, and all offline smokes
npm run smoke:host is a live check against GitHub that spends quota, so it is
not part of npm run check. Smokes, layout, and releasing:
reference; module map:
architecture.
License
Comments
Loading…
Similar plugins
DSH GitHub connector: review PRs, triage issues, debug CI, prepare changes (18 tools, gh-first + REST fallback, approval-gated writes).
★ 0
dsh plugin --profile web add harness-githubby kaziii
DeepSeek Harness (dsh) 的 GitHub 连接器:一键授权,对话内创建/AI 审查/合并 PR | GitHub connector for dsh: one-click connect, create/review/merge PRs from the conversation
★ 12
↓ 23/wk
MIT
TypeScript
Aug 17, 2026
dsh plugin --profile web add dsh-github-connectby caimc21069065-prog
GitLab panel in the DSH right sidebar: commit graph, branches, changes, merge requests (inline diffs, review submission, pipelines), issues, and agent tools with an approval queue for triage and batch
★ 2
NOASSERTION
JavaScript
Nov 1, 2026
dsh plugin --profile web add dsh-gitlab-panelby kx121
到点叫醒 DSH 会话,翻你关注的 GitHub 仓库和主题,挑出值得跟的变化,写日报、记判重表。只读。
★ 2
MIT
JavaScript
Oct 23, 2026
dsh plugin --profile web add dsh-github-digestby apcamargo
Adds /review and /end-review code-review commands to DeepSeek Harness
★ 0
MIT
JavaScript
Oct 19, 2026
dsh plugin --profile web add @apcamargo/dsh-reviewby PerryLink
Official-grade GitHub CI for DeepSeek Harness: composite action.yml, PR review bot with idempotent inline comments and a status-check gate, plus PR/issues tools with every write gated by human approva
★ 33
↓ 775/wk
Apache-2.0
TypeScript
Nov 21, 2026
dsh plugin --profile web add @perrylink/dsh-github