Skip to content
dsh.fish
Bundle

dsh-input-history

Arrow-key input history for the DeepSeek Harness Web composer

Source
NightsVesa
stars
1 stars
License
MIT
Updated
Updated yesterday

Readme

# dsh-input-history

Input history for the DeepSeek Harness Web composer. In any loaded session, press `ArrowUp` to recall older submitted prompts or slash commands and `ArrowDown` to move forward and restore the draft you were typing.

## Install from GitHub

```sh
dsh plugin --profile web add github:NightsVesa/dsh-input-history
dsh web
```

The repository commits its built `lib/` artifacts, so GitHub installation does not run a `prepare` script or require a pnpm `allowBuilds` entry. For a reproducible install, pin a commit:

```sh
dsh plugin --profile web add github:NightsVesa/dsh-input-history#<commit>
```

Remove it with:

```sh
dsh plugin --profile web remove dsh-input-history
```

## Behavior

- History is isolated per session and capped at 256 entries.
- Existing user messages, steering messages, and slash commands are read from the loaded durable session window.
- An open command/reference menu keeps ownership of the arrow keys.
- Modified arrow chords, IME composition, read-only input, and inactive composer states retain their native behavior.
- Reaching the newest entry with `ArrowDown` restores the draft that existed before navigation began.

## Development

Requires Node.js `^22.19.0` or `>=24.0.0` and pnpm 11.7.0.

```sh
pnpm install
pnpm run check
```

The plugin is a standard DSH bundle: `package.json` declares `dsh.bundle`, `cordis.patch.yml` inserts the plugin, and the browser half is exposed through `./client` with a `dsh.client` manifest.

## Compatibility

Tested against DeepSeek Harness `0.1.0-rc.5`. The browser integration targets the stock composer's public `data-composer-card` marker and the client runtime's `sessions` service.

## License

MIT

Install

dsh plugin --profile web add github:NightsVesa/dsh-input-history

Profile: web

  • This package builds from source on install. pnpm will ask you to allow its build script — that is permission to run the package’s code on your machine, outside the agent sandbox. Only allow sources you trust.
  • This source has no pinned commit, so a later push upstream changes what installs. Prefer pinning a commit.
Source