Product subagent retries and transport fallback are invisible behind “Deep diving…”

[Jokasa7]

During a real DeepSeek Harness → Codex → DeepSeek run, the delegated task eventually succeeded, but the Web UI hid five retries and a transport fallback behind one generic status.

Environment

• Windows
• DeepSeek Harness dsh-v0.1.0-rc.8
• @deepseek-ai/dsh-subagent-codex@0.1.0-rc.8
• Bundled @openai/codex@0.147.0
• Foreground subagent_codex call from a Web Session

Reproduction

1. Install the rc.8 Codex Profile Bundle and restart the Profile.
2. Copy the standard Agent Preset and enable its subagent_codex tool row.
3. Start a new Session on that Preset.
4. Invoke subagent_codex.
5. Compare the Web tool card with Host stderr.

Expected

The UI should expose a redacted operational timeline such as:

Codex · provider codex
Starting runtime
Sampling request timed out · retry 3/5
Switching transport to HTTP
Running · 01:42

It should not expose endpoints, prompts, commands, paths, raw stderr, environment values or credentials.

Actual

Host stderr showed retries 1/5 through 5/5:

stream disconnected - retrying sampling request (.../5 in ...)...
sampling_error: request timed out

It then showed:

falling back to HTTP

The Web UI continued to show only Deep diving... and elapsed time.

The operation eventually succeeded. The completed Trajectory correctly showed IN, OUT and a tool duration of 132,548 ms, but the user could not tell during execution whether the run was healthy, retrying, blocked on permission or switching transport.

Suggested resolution

Add a bounded, provider-neutral observation channel on the existing SubagentRun identity. A minimal safe vocabulary could include:

type ProductSubagentObservation =
  | { kind: 'stage'; stage: 'starting' | 'reasoning' | 'finalizing' | 'teardown' }
  | { kind: 'sampling-retry'; attempt: number; maxAttempts: number; reason: 'timeout' | 'disconnect' }
  | { kind: 'transport-fallback'; from: 'sampling'; to: 'http' }
  | { kind: 'compatibility-warning'; code: 'codex-model-cache-schema' }

The UI should render these fixed events, not raw product protocol messages.