Shikitor editor and sender surfaces for DeepSeek Harness
The plugin will be installed here. Keep web if you are unsure.
npx -y @deepseek-ai/dsh plugin --profile web add dsh-shikitor@1.0.2
Compatibility and provenance
Shikitor is published as dsh-shikitor and currently resolves to version 1.0.2. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.
# Sessions Searches the conversations shown in the current workspace sidebar. A selection is inserted as one protected session link using the deepseekharness://sessions/<sessionId> protocol.
@ Workspace files Lists files from the current workspace. When Cordis plugins or subagents contribute candidates, they appear before files. Files are ordered from shallow to deep, loaded incrementally, and can be narrowed with file: or plugin:. Hidden paths appear only after the query explicitly enters a dot-prefixed segment.
$ Skills Searches merged project, home, and plugin-provided skills. Project-local entries take precedence when names collide, and the chosen skill is converted to DSH's executable /skill-name form.
/ Commands Uses DSH's command catalog together with executable skills. Selection remains inside DSH's original pick transaction, so built-in command behavior and plugin contributions continue to work.
Shikitor editing and completion menus in the DSH message sender;
a file editor tab for the current workspace;
a Cordis ctx.shikitor service that other client plugins can extend.
Completion menus support pointer selection, Arrow Up/Down, Enter/Tab, and
Escape. Workspace files are ordered from shallow to deep and loaded into the
menu incrementally while scrolling. The Message sender settings can further
limit file search with comma-separated include/exclude folder globs. Accepted
file references render only the filename. Cmd-click
(Ctrl-click on Windows or Linux) opens the referenced workspace file in the
Shikitor editor tab.
Skill discovery covers <projectRoot>/{.agents,.codex,.claude,.oo}/skills and
the matching directories under the user's home. Project entries win duplicate
names from home entries.
Register a surface plugin
import type {} from 'dsh-shikitor/client'
import type { ClientContext } from '@deepseek-ai/dsh-client-runtime/client'
import mySenderPlugin from './my-sender-plugin.ts'
export const inject = ['shikitor']
export function apply(ctx: ClientContext) {
ctx.effect(
() => ctx.shikitor.register('sender', mySenderPlugin),
'my-plugin: Shikitor sender contribution',
)
}
Use sender for message-composer behavior and editor for file-editor behavior.
Register the same Shikitor plugin on both surfaces when they should share it.
The default filename mapping, glyphs, fonts, and colors come from
Atom File Icons. Rules can match
extensions, exact fileNames, or a custom match function. Their icon may
be an Atom File Icons class list or a DOM renderer. Higher priority wins;
equally ranked rules prefer the most recently registered contribution. The
disposer removes only that plugin's rule.
General settings also expose browser-persisted path rules. Each rule accepts a
glob (* within one path segment, ** across folders) and can select any Atom
glyph or an image. Image sources may be HTTP(S)/data URLs, workspace-relative
paths, or absolute paths inside the current workspace. Workspace images must
use a supported image type and be no larger than 1 MiB. Later user rules win.
Plugins can observe the same effective registry through
fileIconRules; the editable rules are exposed separately through
configuredFileIconRules and configureFileIconRules().
The General settings tab owns the shared color scheme, highlight-theme family,
cursor shape, and file-icon policy. Sender and File editor inherit that
appearance until their first surface-specific change;
resetSurface() removes the override and resumes live inheritance. Editor-only
line/current-line controls remain on the File editor tab. These browser-local
appearance values are also available through ctx.shikitor.appearance,
resolveAppearance(), and configureAppearance().
Edited files save automatically by default. Auto save can be disabled in the File editor settings; the editor toolbar and Cmd/Ctrl+S remain available for manual saves. Plugins can read and update this behavior through ctx.shikitor.preferences and configurePreferences().
