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.
Who it is forA developer building a web or agent project who switches constantly between editing files, running commands, and previewing output.
The problemKeeping 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 outcomeOne project opens as a split workspace with a saved layout, draggable dividers, and per-pane tabs for files, terminal, and preview.
What you need first
- A working DeepSeek Harness (dsh) install with the web profile, or the Desktop app on Windows for the tested Desktop scope
- Node.js and npm if you plan to clone the repo and build from source
- A browser where you can keep the same origin, since projects and layouts are stored in browser localStorage
Steps
- Complete the install and restart steps for the web profile first.
- In the sidebar, click + and choose a layout preset such as left column, top row, or main grid with right chat pane.
- Set the project folder so the file explorer and file panes point at the right directory.
- Open the built-in panes you need: file explorer, terminal, browser, animation site, or custom window.
- Drag the dividers to resize panes; the width is saved per layout.
Prompt for your agent
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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page