DSH / PLUGIN / SESSIONS

dsh-session-title-first-prompt-llm

v0.1.0-rc.5deepseek-ai / deepseek-harness47f943859b

Included in DSHPluginsSessions & contextBuilt-in sourceConfigurable
Runtime anatomy
HOSTCLIENTUITOOLDATAFLOW

Overview

dsh-session-title-first-prompt-llm

Optional ctx.sessionTitle provider that summarizes the first eligible human message through ctx.llm. It registers the first-prompt cadence, runs automatically only when a fresh non-fork session first creates its fallback, and attributes the result to that message's exact seq. An automatic failure retains the fallback and is retried only through ctx.sessionTitle.refresh().
BUILT-IN / ATOMIC
Already shipped with DSH — no separate install

This is an atomic module already shipped with Harness, not a standalone profile layer.

Capabilities

What it contributes

HostCordis loadableConfigurable
Client / UIHost only0 contributions
Model tools0None declared
Profile stateenabledbase, headless, web

README / EN

Package documentation

@deepseek-ai/dsh-session-title-first-prompt-llm

English | 中文

Optional ctx.sessionTitle provider that summarizes the first eligible human message through ctx.llm. It registers the first-prompt cadence, runs automatically only when a fresh non-fork session first creates its fallback, and attributes the result to that message's exact seq. An automatic failure retains the fallback and is retried only through ctx.sessionTitle.refresh().

The plugin uses the complete required shared LLM configuration. Omit both provider and model to inherit the exact route from the current logged main request, or set both to route title generation independently.

Model Experience

First-message title request

What the model sees

The title model receives the shared title instruction and a JSON array containing only the first eligible human message. Later prompts and inherited fork history do not trigger another automatic call.

Token effect

At most one automatic auxiliary request is made for a fresh session, bounded by maxInputBytes and maxOutputTokens; explicit refreshes may make additional calls. The main agent request gains zero tokens.

KV Cache effect

No main-request invalidation. The auxiliary request uses the configured or logged route and has provider-specific cache behavior.

Known Limitations and Deferred Work

  • The first message alone may cease to represent a long-running session; use the all-messages provider when later prompts should retitle it.
  • A fork keeps its inherited title and never runs this provider automatically, even when its seeded first message came from the parent.

LIMITATIONS

Known limitations

- The first message alone may cease to represent a long-running session; use the all-messages provider when later prompts should retitle it. - A fork keeps its inherited title and never runs this provider automatically, even when its seeded first message came from the parent.