NEWdsh-flykit is live — turn the DeepSeek Harness web GUI into an agent cockpit
flykit.cc

Getting started

Install flykit

Three steps to the cockpit, then the plugins that sharpen the agents you run inside it.

Part one — the cockpit

The cockpit is a plugin for DeepSeek Harness, the open-source agent harness that powers it. Nothing is hosted: the harness, the panel and every agent you start run on your machine.

01

Install the harness

The dsh CLI carries the agent, the web UI, and the plugin loader. Node 22 or newer.
$ npm install -g @deepseek-ai/dsh
02

Add the cockpit

A dsh plugin extends the harness itself — new panels, new tools, new routes. There is no marketplace to register: the name is an npm package.
$ dsh plugin --profile web add dsh-flykit
03

Open it

Start the web UI and open the link it prints. The panel is on the right of every session — Explorer for your files, Agents for the terminals. Remove a plugin again with dsh plugin --profile web remove <name>.
$ dsh web

Part two — arm your agents

Claude Code plugins bundle skills, slash commands, subagents and hooks. They work the same whether you run Claude Code in your own terminal or in an Agents tab inside the cockpit.

04

Install Claude Code

Get it from docs.claude.com. Any recent version supports plugins. Pi and Codex install from their own projects and need no setup here.
05

Add the marketplace

Register flykit as a plugin marketplace. You only do this once.
$ claude /plugin marketplace add flykit-cc/plugins
06

Install a plugin

Pick one from the catalog and install it scoped to flykit.
$ /plugin install flow@flykit
07

Mind the working directory

Claude Code takes the folder you launch it from as the session's working directory. Inside the cockpit that folder is the session's workspace, already correct. In your own terminal it depends on the plugin:
  • Skills that touch files (like steuer, which reads bank exports and writes reports) — cd into the folder where your data lives.
  • Slash commands, subagents, and prompt-only plugins — the folder doesn't matter.
  • Hooks and MCP servers — context depends on the plugin. Check its README.
08

Run a skill

Each plugin exposes one or more skills. Invoke them like any other slash command.
$ /flow:continue

Uninstalling

Remove a single plugin, or unregister the whole marketplace.

Remove one plugin:

$ /plugin uninstall steuer@flykit

Unregister the marketplace entirely (also removes every plugin installed from it):

$ /plugin marketplace remove flykit

What next?

Read what the cockpit can do, browse the catalog, or open an issue to request a new one.