mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-11-09 20:07:43 +08:00
The persisted draft now records the leading command chip's claim token (DraftSnapshot.command). Restoring the draft asks the trigger pipeline's new resolveClaim, which polls the optional InputTriggerSource.matchClaim hook: the command source awaits its catalog and answers only a leadingInput claim, never opening a popup, running an action, or executing the command. The input rebuilds the chip once the claim resolves, only at the revision the restore produced and merged into the seed's history entry; otherwise the literal token stays and Enter still adjudicates it.