[Bug]: background completion reminders arrive only after active parent turn ends in v4.2.2

[NICxKMS]

Prerequisites

• I am writing this issue in English.
• I searched existing issues and found related but not exact matches.
• I am using the latest version of oh-my-openagent.
• I checked the documentation / investigated with the repo context loaded.
• I ran npx -y oh-my-openagent doctor and included the output below.

Bug Description

Background task completion reminders still appear to be delivered too late in oh-my-openagent v4.2.2.

A background child session can finish quickly, but the parent model does not receive [BACKGROUND TASK COMPLETED] or [ALL BACKGROUND TASKS COMPLETE] while its current turn is still active. The reminder is injected only after the parent turn ends and the parent has already sent its final response.

Steps to Reproduce

1. Start a parent agent turn.
2. Launch a trivial background task:

task(
  category="quick",
  load_skills=[],
  run_in_background=true,
  description="Hi only session",
  prompt="Respond exactly with `hi` and then stop."
)

3. Keep the parent turn active with harmless file reads and sleeps for about a minute.
4. Observe that the child session completes.
5. Observe that no completion reminder reaches the active parent turn.
6. Let the parent send its final response.
7. Observe that [ALL BACKGROUND TASKS COMPLETE] arrives only after the parent turn has ended.

Expected Behavior

The active parent turn should receive the background completion reminder before it finalizes, so it can call background_output(...) during the same turn.

Actual Behavior

The child task completed in about 5 seconds, but no reminder reached the active parent turn.

Observed task:

• Background task ID: bg_e8c2b5ef
• Child session ID: ses_1c46e2af9ffeBguUcCF8zy5QVF
• Child output: hi
• Task duration: 5s

The parent stayed active for roughly a minute. After the parent final response, this arrived:

[ALL BACKGROUND TASKS COMPLETE]

Completed:
- bg_e8c2b5ef: Hi only session

After that, background_output(task_id="bg_e8c2b5ef") returned hi.

Doctor Output

$ npx -y oh-my-openagent doctor

oMoMoMoMo Doctor

✓ System OK (opencode 1.15.4 · oh-my-openagent ^4.2.2)

Error Logs

No exception or crash was observed. The failure is delayed notification timing.

Configuration

opencode --version:

1.15.4

npx -y oh-my-openagent --version:

4.2.2

C:\Users\Nicx\.config\opencode\opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "oh-my-openagent@^4.2.2"
  ],
  "provider": {},
  "mcp": {
    "stitch": {
      "type": "remote",
      "url": "https://stitch.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "<redacted>"
      },
      "enabled": true
    }
  }
}

C:\Users\Nicx\.config\opencode\oh-my-openagent.json relevant excerpt:

{
  "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/assets/oh-my-opencode.schema.json",
  "team_mode": {
    "enabled": true,
    "tmux_visualization": false,
    "max_parallel_members": 8,
    "max_members": 8,
    "max_messages_per_run": 10000,
    "max_wall_clock_minutes": 120,
    "max_member_turns": 500,
    "message_payload_max_bytes": 327680,
    "recipient_unread_max_bytes": 2621440,
    "mailbox_poll_interval_ms": 3000
  },
  "agents": {
    "sisyphus": {
      "model": "openai/gpt-5.5-fast",
      "variant": "xhigh",
      "fallback_models": [{ "model": "openai/gpt-5.5", "variant": "xhigh" }]
    },
    "sisyphus-junior": {
      "model": "openai/gpt-5.5-fast",
      "variant": "xhigh",
      "fallback_models": [{ "model": "openai/gpt-5.5", "variant": "xhigh" }]
    }
  },
  "categories": {
    "quick": {
      "model": "openai/gpt-5.5-fast",
      "variant": "xhigh",
      "fallback_models": [
        { "model": "openai/gpt-5.5-fast", "variant": "xhigh" },
        { "model": "openai/gpt-5.5", "variant": "xhigh" }
      ]
    }
  }
}

Additional Context

v4.2.2 includes the relevant parent-wake fixes and ParentWakeNotifier, but this live repro still shows delayed delivery.

Related but not exact duplicates:

• background_output still returns 'Task not found' after PR #4015 (macOS + Windows) #4095: background_output returns Task not found. Different issue; here background_output works after the delayed reminder arrives.
• [Bug]: Desktop sidecar crash with napi_fatal_error (SIGABRT) after agent completion — macOS arm64, v4.1.2 #4120: parent-wake/background completion timing around Desktop crash. Different symptom; this repro is delayed active-parent delivery.

Operating System

Windows

OpenCode Version

1.15.4

[ririnto]

I observed what looks like a related failure mode.

The parent agent did not receive/use the background result during its active turn, concluded that the subagent had not responded, called background_cancel, and finalized its own response. Later, the same parent session received [BACKGROUND TASK COMPLETED], but it did not follow up by reading the child session or calling background_output; it treated the task as already handled.

So the delayed reminder can cause more than a missed background_output: it can arrive after the parent has already made a cancellation/finalization decision, and the completed result is not reliably inspected afterward.

[Yeachan-Heo]

Additional Discord feedback from UltraWorkers #omo-help (2026-05-19) appears to match the same parent-wake/background completion timing class.

Observed symptoms reported:

- OMO often loses track / gets stuck / stops tasks
- main task can end without waiting for a subagent it called to finish
- shell/tool use can appear stuck forever
- sending a follow-up wakes it up
- screenshots show repeated stuck states, not a one-off rare case
- reported with GPT and Gemini providers

This strengthens the likely invariant for this issue:

If a child/background/subagent state changes while the parent turn is still alive, the active parent must receive a wake/completion/failure signal during that turn, not only after a new user message or after the parent has already finalized.

It may overlap with #3774 / #3255, but the key extra signal here is "follow-up wakes it up", which points at event delivery/turn wakeup rather than only result retrieval.

—
*[repo owner

[SIPHON2936]

+1, the same issue.

[masterkain]

not fixed