Open Sea Skin for DeepSeek Harness: an ocean theme that keeps your new-tab page

What Open Sea Skin actually solves, and the name collision you should clear up first

DeepSeek Harness is a workspace, and a workspace with a flat background is a workspace you stop noticing. Open Sea Skin replaces that background with an animated ocean rendered in real time: waves, reflections, and a light that moves from daylight through sunset. It also makes the Harness interface translucent, with glass opacity adjustable from 40% to 90% in both light and dark layouts. The README describes the effect as "a living ocean behind your workspace" and is explicit that this is not a looping wallpaper video.

The audience is narrow and clearly stated. This is a skin for DeepSeek Harness, not for the DeepSeek chat website, and it is community-made rather than an official DeepSeek product. The README also pre-empts the most likely search confusion: the project is unrelated to the OpenSea NFT marketplace. If you arrived here looking for a marketplace, a token, or anything with a price, you are on the wrong page, and the related-search data suggests a lot of people make that mistake.

What you get is cosmetic. There is no productivity claim, no agent behaviour change, no data layer. That honesty is a point in the project's favour: it does one visual thing and documents the boundaries of that thing.

How the ocean is rendered: WebGPU, local assets and a Harness-only injection rule

The rendering path is a real-time WebGPU scene, not a video. package.json describes the package as a "Realtime WebGPU ocean skin for DeepSeek Harness on Chrome and Edge", and the topics list includes both threejs and webgpu. The README states that ocean scripts, three.js and fonts ship with the skin, and that there are no skin analytics or runtime CDN requests. That matters more than it sounds: a background layer that phones out on every page load is a different product from one that does not.

The extension has a gate. According to the README, it verifies the Harness page before injecting the ocean, so other local development pages are left alone. The extension targets Harness pages served on 127.0.0.1 or localhost. It does not replace new tabs and does not change your browser homepage, which the README lists as a feature rather than an omission.

The plugin route is packaged differently. The npm package exposes plugin/index.js as its main entry, plus a client entry and a cordis.patch.yml patch file, and declares a dsh bundle pointing at that patch with a web platform client. So the DSH plugin is a bundle patch applied to Harness rather than a script tag appended to a page. The static installer is the third path, and it is the blunt one: it edits built frontend files directly.

One accessibility detail is worth flagging as a design choice rather than a feature bullet. The README lists reduced-motion support and Escape-to-close alongside keyboard navigation. A full-screen animated ocean is exactly the kind of element that needs an off switch, and the project appears to have one.

Installing Open Sea Skin as a DSH plugin and tuning your first sea state

Pick one installation method. The README says installing several at once makes updates and troubleshooting harder, and given that three channels exist, that warning is not decorative.

For Harness Web or the DSH plugin installer, the prebuilt npm route avoids a Git download and an install-time build:

dsh plugin --profile web add [email protected]

The README is specific about why you would pin 1.2.3: npm was still at 1.2.3 while GitHub carried v1.2.4, and the language-sync fix landed in v1.2.4. To get that fix from the published tag instead:

dsh plugin --profile web add 'github:d-dev0101/open-sea-skin#v1.2.4'

After either command, restart Harness and reload its page. The skin settings panel appears at the lower left. In DSH Desktop the README points to the managed plugin installer and a restart from Desktop settings, noting that available update versions depend on the catalog and installation source.

If you would rather use the browser extension, download the extension ZIP from the v1.2.4 release, unzip it, open chrome://extensions or edge://extensions, enable Developer mode, choose Load unpacked, and select the extracted folder containing manifest.json. If you cloned the repository, select extension/. Then open your Harness page on 127.0.0.1 or localhost and reload it.

The static installer is for a built Harness frontend that cannot use the plugin. Stop Harness first, inspect the script, then run:

curl -fsSL https://raw.githubusercontent.com/d-dev0101/open-sea-skin/main/install.sh | bash

Start dsh web again and keep it running. After a Harness frontend upgrade, rerun with the update flag:

bash -s -- --update

The README is clear that this method changes frontend files and does not start the server. It also points to native-dist/README.md for explicit frontend paths, backups and recovery, which tells you the authors expect people to need the rollback path.

Once installed, the controls are three sliders in the lower-left panel. The gallery recordings use wave size 56 and daylight Afternoon (55) at 40% glass opacity, so those numbers are a reasonable starting point if you want to reproduce what the screenshots show.

Where Open Sea Skin is the wrong tool

The static installer is the sharpest limitation. It rewrites frontend files of a built Harness distribution. Any Harness frontend upgrade can overwrite that work, which is why the README instructs you to rerun the installer with --update afterwards. If you cannot tolerate a shell script modifying your installed frontend, use the plugin or the extension instead. The README itself frames the static path as the fallback for frontends that cannot take a plugin, not as the preferred route.

Version skew is the second trap. The README's release-status line, checked September 12, 2026, records GitHub at v1.2.4 and npm at 1.2.3, and warns against using [email protected] until it appears on npm. If you install by version number from the wrong registry, you either get an older build or a resolution failure, and the language-sync fix is the thing you miss.

Hardware and browser support is the third. The scene is WebGPU. The README does not publish a fallback rendering path, so on a browser or machine without WebGPU support the ocean has no documented alternative. That is a real constraint for anyone on an older GPU, a locked-down corporate browser, or a virtualised desktop.

Finally, this is a cosmetic layer. It does not make Harness faster, and a continuous animated background consumes GPU time that your machine would otherwise spend elsewhere. The project makes no performance claim in the repository documentation, and the README does not document a frame-rate budget or an idle mode. If you are already GPU-bound, adding a real-time ocean is the wrong direction.

Open Sea Skin versus a plain CSS gradient theme

The obvious alternative is a static theme: a CSS gradient or a fixed background image applied to Harness through a user stylesheet or a simple extension. The difference in approach is the whole point of this project. A gradient costs nothing per frame, works on any browser that renders CSS, and never needs a GPU feature check. It also cannot move.

Open Sea Skin trades that for a real-time WebGPU scene with adjustable wave size and a light that shifts from Midday to Dusk, plus a glass layer over the interface. The README's own framing of the trade is "Watch animated waves and reflections, rather than a looping wallpaper video", where the comparison is against video backgrounds, the other common way to get motion without a renderer. A video loop is heavier on disk and bandwidth but lighter on GPU logic; a WebGPU scene is the opposite.

If your goal is only to stop looking at a white rectangle, a gradient is the cheaper answer and you should take it. If your goal is a background that responds to sliders, Open Sea Skin is the more direct fit, and the interactive demo on the project site is the honest way to decide before you install anything.

Maintenance, upgrade paths and what the MIT licence does not cover

The repository is not archived, and the last push was on 2026-09-11. Releases are close together: v1.2.2 on 2026-09-01, v1.2.3 on 2026-09-07, and v1.2.4 on 2026-09-09. The changelog titles are narrow and specific (a language sync fix, a DSH Desktop glass fix), which suggests small, targeted patches rather than periodic rewrites.

Upgrade cost depends entirely on which channel you chose. The plugin route is a version bump through dsh plugin add, with the caveat that DSH Desktop updates depend on the catalog and installation source. The extension route means repeating the unpacked-folder dance with a new ZIP, since the README's steps are manual and there is no store listing mentioned. The static route means rerunning install.sh with --update after every Harness frontend upgrade. Three channels, three different maintenance rhythms.

On licensing: the project is MIT, and the repository carries a THIRD_PARTY_NOTICES.md alongside the LICENSE file. The README states that three.js and fonts ship with the skin as local assets. MIT covers the project's own code, but bundled third-party components carry their own terms, and the notices file is where those are recorded. Read it before redistributing a build or shipping the extension inside another product. That is a description of where the information lives, not legal advice.

Editorial conclusion

Adopt Open Sea Skin if you run DeepSeek Harness on localhost and want a live ocean background with a glass interface, and you accept that a WebGPU compositor is running under your chat window. Do not adopt it if you expected the OpenSea NFT marketplace, if you are on a browser without WebGPU, or if your Harness frontend was built without plugin support and you would rather not let install.sh edit frontend files. Verify two things before you commit: which installation channel you are on, since npm is at 1.2.3 while GitHub carries v1.2.4, and whether your reduced-motion setting is the behaviour you want.

Frequently asked questions

Official sources

1. d-dev0101/open-sea-skin on GitHub
2. License: MIT
3. Project website
4. README
5. Releases