# AI use cases for DSH Worktable (Aisland-SJL/dsh-worktable)

Repo: [Aisland-SJL/dsh-worktable](https://github.com/Aisland-SJL/dsh-worktable) | Use cases: 4 | Page: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/

dsh-worktable is a Cordis plugin for DeepSeek Harness that adds a sidebar app drawer, a dockable split workspace for each project, and a control room that mirrors the status of every bound project.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Watch every agent project status from one control room: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/watch-all-agent-projects-in-control-room/
- Work on a project in one split window with files, terminal, and browser: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/run-multi-pane-project-workspace/
- Point at a window element and send a fix request to the agent: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/hand-ui-fixes-to-agent-with-point-annotate/
- Turn a written requirement into a live window in the workspace: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/build-custom-window-from-requirement/

## How to watch every agent project status from one control room with DSH Worktable

Repo: [Aisland-SJL/dsh-worktable](https://github.com/Aisland-SJL/dsh-worktable) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Install the plugin and bind one conversation to get a live card grid of working, needs-you, and done projects.

**Who it is for:** A developer running several agent projects in DeepSeek Harness who keeps losing track of which one is waiting for input.

**The problem:** Agent projects run in separate conversations, so checking whether each one is busy, blocked, or finished means opening them one by one.

**The outcome:** A pinned control-room card shows each bound project as working, needs you, or done, with a short cleaned message preview.

### Steps

1. Install the plugin with `dsh plugin --profile web add "https://github.com/Aisland-SJL/dsh-worktable/releases/latest/download/dsh-worktable.tgz"`
2. If the `dsh` command is missing, run `npx @deepseek-ai/dsh` in its place with the same arguments.
3. Restart the DSH web process and refresh the GUI.
4. Click the pinned 🖥️ control-room card, then bind one conversation by joining an existing one or creating a new one.
5. Open the sidebar ＋ for each agent project, choose a layout preset, and set its project folder and bound conversation so it appears on the card grid.

### Prompt to paste into your agent

```text
Use the repo Aisland-SJL/dsh-worktable to set up the control room in DeepSeek Harness web at <harness-url>. Report the card grid state for each bound project (working, needs you, or done). Verify that projects with no bound conversation show as idle.
```

### Caveat

The control room only monitors projects that are bound to a conversation, and all project state stays in the browser's localStorage and IndexedDB rather than syncing across machines.

Risk, remote script: The install command pulls a tarball from a GitHub Release and registers it in your DSH profile, which may ask for authorization and writes to ~/.dsh, so check the source URL before running it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/watch-all-agent-projects-in-control-room/

## How to work on a project in one split window with files, terminal, and browser with DSH Worktable

Repo: [Aisland-SJL/dsh-worktable](https://github.com/Aisland-SJL/dsh-worktable) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Open a project as a dockable workspace that combines file explorer, terminal, browser, and chat in one layout.

**Who it is for:** A developer building a web or agent project who switches constantly between editing files, running commands, and previewing output.

**The problem:** Keeping an editor, a terminal, a browser preview, and an agent chat side by side in separate windows is slow to set up and lost on every reload.

**The outcome:** One project opens as a split workspace with a saved layout, draggable dividers, and per-pane tabs for files, terminal, and preview.

### Steps

1. Complete the install and restart steps for the web profile first.
2. In the sidebar, click ＋ and choose a layout preset such as left column, top row, or main grid with right chat pane.
3. Set the project folder so the file explorer and file panes point at the right directory.
4. Open the built-in panes you need: file explorer, terminal, browser, animation site, or custom window.
5. Drag the dividers to resize panes; the width is saved per layout.

### Prompt to paste into your agent

```text
Using the repo Aisland-SJL/dsh-worktable in DeepSeek Harness, create a project for <project-folder> with a split layout that includes file explorer, terminal, and browser panes. Report the layout name and pane list. Verify that reopening the project restores the same panes and widths.
```

### Caveat

The terminal pane is a plain PowerShell host on Windows with no PTY feature parity with the native terminal app, and layouts do not sync between Web and Desktop origins.

Risk, credentials: The terminal pane runs a PowerShell host on Windows and its commands can reach files and the network, so do not paste secrets into it that you would not give the commands.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/run-multi-pane-project-workspace/

## How to point at a window element and send a fix request to the agent with DSH Worktable

Repo: [Aisland-SJL/dsh-worktable](https://github.com/Aisland-SJL/dsh-worktable) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Click a spot in a window, type the change, and load a packaged annotation into chat for the agent to act on.

**Who it is for:** A developer reviewing a rendered window who wants to request a visual change without describing its location in words.

**The problem:** Describing which element to change and where it sits takes several messages and often leads to the wrong element being edited.

**The outcome:** The chat input receives a packaged message with the window number, coordinates, clicked element, and your request, ready to send.

### Steps

1. Open the window you want to change inside a project workspace.
2. Click the small annotate button (chat bubble with a plus) in that window's title bar.
3. Click the spot in the window where the change belongs, type your request such as "make this text bigger", and press ✓.
4. Review the message that fills the chat input; it is not sent yet.
5. Press Enter to send it when ready, then check the agent's result with a screenshot or the window itself.

### Prompt to paste into your agent

```text
In the repo Aisland-SJL/dsh-worktable, a user has sent a point-to-annotate message for window <window-number> at <coordinates>. Apply the requested change to the target element, report which element was changed, and verify the result with a screenshot before finishing.
```

### Caveat

The annotation is only filled into the chat input and is not sent automatically, so you still need to press Enter yourself.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/hand-ui-fixes-to-agent-with-point-annotate/

## How to turn a written requirement into a live window in the workspace with DSH Worktable

Repo: [Aisland-SJL/dsh-worktable](https://github.com/Aisland-SJL/dsh-worktable) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Send a requirement to a conversation so the agent builds a result that auto-mounts into a locked custom window.

**Who it is for:** A developer who wants a small tool or page built by an agent and shown directly beside their project.

**The problem:** Agent-built output usually lands in a file or chat message and has to be opened and placed by hand each time.

**The outcome:** The agent's finished result appears inside the custom window in the project layout, and the window is locked against accidental edits.

### Steps

1. Open the target project and the window where the result should appear, then choose Custom.
2. Write the requirement and send it to a new conversation or an existing one.
3. Let the agent build the result; it writes a dedicated result under `.dsh-worktable/project-` in the project folder.
4. Check that the result auto-mounts into the window and is locked.
5. If an old conversation no longer mounts results, use the window's Custom → Send to conversation action once to re-enable it.

### Prompt to paste into your agent

```text
Using Aisland-SJL/dsh-worktable, take the requirement <requirement-text> for project <project-name>, have the agent build it in a custom window, and report the result file path. Verify that the output mounts automatically into the locked custom window and that the file is under .dsh-worktable/.
```

### Caveat

Auto-mount needs a registered custom task and a matching v2 result file, and shared-folder projects can overwrite the same artifact if told to write the same physical file.

Risk, credentials: The agent writes and runs whatever the requirement asks for inside your project folder, so review the requirement and result before sharing the project.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/aisland-sjl-dsh-worktable/build-custom-window-from-requirement/