dsh-step-clock

The built-in turn timer only appears after 15 seconds and measures the entire turn, not the single step currently in flight. When you are watching a bash call that has been running for minutes, you cannot tell whether it started two seconds ago or has been stuck for four minutes, and the turn clock cannot help. dsh-step-clock embeds a lightweight elapsed-time bar in the composer dock that ticks from 0:00 with no delay threshold, answering one question the harness leaves unanswered: how long has the current step actually been running?

Tool steps are anchored to the launch time of the tool call itself, so 0:47 means that specific call has been running for 47 seconds, not a turn-level estimate. Thinking steps fall back to the step boundary, the closest honest anchor for model time. Instead of a bare number, the bar states the situation in plain language: running bash with two other tools in parallel, the model is thinking, or a step has just finished and took 3 minutes 45 seconds. When a step completes its duration stays on screen until the next step replaces it; if start and end timestamps are missing the bar reports idle rather than inventing a number.

Ideal for DeepSeek Harness web users who regularly monitor long-running bash calls, parallel multi-tool steps, or need to pinpoint which step slowed a turn down the most. Durations are rendered in natural phrasing so that 0:03 is never ambiguous and every second of a slow step is accounted for.