# Live OpenCode background question comparison

Both sides: Linux web dev server from separate commit worktrees, fresh T3 database with T3CODE_DEV_SEED=0, isolated OpenCode 2.3.0 XDG directories, Chromium 1440x1000 CSS pixels at device scale 2, dark theme. One synthetic git project named Color demo. The auto-created server project and empty thread were removed through the CLI on both sides before capture. No previous attempts were reused.

Base: 2579c3c4dd25c2a8572af53724b7cd6e87643483.
Head: ebcad39182b6f64230ef492d6e6935a173efdf58.

The seed.py file records the equivalent setup performed through Python, git, and T3's project CLI. Supply a local credential-bearing OpenCode config; credentials are intentionally excluded. Install @opencode/cli@2.3.0 into a scratch npm prefix and pass its binary path. Install each checkout with vp i. Start each with T3CODE_DEV_SEED=0 vp run dev.

Browser actions on each side:
1. Pair with that side's server. Select New thread and Color demo. Hide the thread details panel, keeping the sidebar visible.
2. In the model picker, search haiku and select Claude Haiku 5.5 from OpenCode / Anthropic. Permissions: Full access. Current checkout, main.
3. Enter this exact prompt and start recording immediately before submitting:

> Use the Task tool to launch one general subagent in the background with this task: "Use your question tool to ask the user one single-choice question, 'Which color?', with options Red and Blue, then reply CHILD-PICKED=<label>." Right after launching it, run `sleep 30` in the foreground, then reply LAUNCHED. When the subagent reports, reply PARENT-GOT-<label>.

4. Leave Which color? unanswered while sleep 30 runs. Wait for LAUNCHED and parent completion.
5. Base: the question disappears, so no answer can be selected; stop the recording with the child still Running and Waiting. OpenCode still has the pending form. Parent completion and request cancellation both occur at 17:38:13.054 UTC.
6. Head: the same question remains visible after LAUNCHED; runtime request remains pending despite parent completion at 17:39:58.865 UTC. Click Red at 17:40:19 UTC. This single-choice card submits immediately; no separate Submit click is required. Observe CHILD-PICKED=Red, child Finished, and PARENT-GOT-Red. Stop the recording after the completed state is visible. Confirm that there is one sidebar thread and no Input badge; reload and confirm again.

Recording landmarks (approximate):
- Before, 0:08: question is visible; 0:39: LAUNCHED arrives and the question disappears.
- After, 0:08: question is visible; 0:40: LAUNCHED arrives and the question stays; 1:01: Red is selected; shortly afterwards child and parent complete, with no Input badge.

Generated parent titles differ (Background Subagent Question Test versus Subagent Question Relay Test); generated child titles also differ. These are live model output from the same prompt, not additional threads. runtime-evidence.json accounts for every thread, including the deleted automatic bootstrap thread on each side.

collect-evidence.py reads only the reproduction databases. Its output includes native child-form responses captured through each spawned OpenCode server's authenticated API, all thread rows, runtime requests, provider-turn status, and the real sleep 30 execution timestamps. The head snapshot taken after parent completion and before answering is included separately. No tests, replay provider, or scripted model were used.

The completed PNG was taken after blurring the composer caret; two captures separated by at least 500 ms were pixel-identical (ImageMagick AE=0). The waiting state is documented by video because its elapsed counters and waiting spinner are inherently dynamic. Both recordings and the completed PNG were visually inspected before upload.

Work performed using GPT-6.1-Sol through the Codex harness.
