[Bug]: Sisyphus wants to works too fast.

[Halloweedev]

Prerequisites

• I will write this issue in English (see our Language Policy)
• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Bug Description

Hi!

Use ulw with a prompt. Starts Oracle delegation, and Sisyphus adds time to the timeout a few times, around 3-4. Then, says: "Oracle is taking a very long time on this deep analysis. I have enough context from my own investigation + explore agents to present findings now. Here's my analysis:"

Starts implementing.

Once done, he says "Oracle's key recommendation: Make the side columns scroll-enabled too and sync via contentOffset instead of frame translation.
This is a fundamentally better approach than what I've done so far."

And reimplements.

The goal of having the Oracle and the other subagents is to being used, not overrides them.
Is there a way to fully enforce Sisyphus to wait the end, no matter the time Oracle takes for his task?

As this is a very big waste of tokens that happens quite a lot.

Steps to Reproduce

1. Start a session with Sisyphus
2. Ultrawork the prompt
3. Sisyphus delegates to Oracle
4. Oracle is too long for Sisyphus
5. Sisyphus decides to continue on his own
6. Sisyphus finishes is implementation
7. Sisyphus checks Oracle findings
8. Sisyphus says it's better
9. Re-implements with new context

Expected Behavior

Sisyphus should WAIT until the subagent is done.

1. Start a session with Sisyphus
2. Ultrawork the prompt
3. Sisyphus delegates to Oracle
4. Sisyphus waits and checks Oracle findings
5. Implements with new context

Actual Behavior

Starts implementing.

Once done, he says "Oracle's key recommendation: Make the side columns scroll-enabled too and sync via contentOffset instead of frame translation.
This is a fundamentally better approach than what I've done so far."

And reimplements.

The goal of having the Oracle and the other subagents is to being used, not overrides them.

Doctor Output

oMoMoMoMo Doctor 

 ⚠ 2 issues found:

1. Loaded plugin is outdated
   Loaded 3.8.5, latest 3.10.0.
   Fix: Update: cd ~/.config/opencode && bun update oh-my-opencode
   Affects: plugin features

Error Logs

Configuration

Additional Context

No response

Operating System

macOS

OpenCode Version

1.2.15

[acamq]

It sounds like Oracle is getting called with run_in_background=true, which would cause the behavior you're describing. However, Oracle shouldn't be getting called with that. Could you provide a screenshot (redacting as necessary) of the conversation that contains the "adding time to a timeout" behavior?

Also, you might want to update your oh-my-opencode to latest (3.10.0) and see if that fixes the issue.