[FEATURE]: Non-blocking background timer / async ping #31335

Activity

1. github-actions

   assigned

   jlongster

   on Jun 8, 2026
2. github-actions commented on Jun 8, 2026

   

   github-actionsbot

   on Jun 8, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • Feature requests must use the [FEATURE]: title prefix (e.g. [FEATURE]: Non-blocking background timer / async ping)
   • Feature requests must use the feature request template, which includes a verification checkbox confirming you have searched for existing issues
   • The issue content appears to be AI-generated. Long, AI-generated walls of text are not acceptable — please rewrite in your own words, concisely describing the problem and what you need

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • [feat] True Async/Background Sub-Agent Delegation #5887: True Async/Background Sub-Agent Delegation — same core request for non-blocking async background task execution while the main chat remains interactive

   If you believe this was flagged incorrectly, please let a maintainer know.

   ❤️React with ❤️1Reacted by Yash Desai
3. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 8, 2026
4. yash-desai-naik commented on Jun 8, 2026

   

   yash-desai-naik

   on Jun 8, 2026

   Author

   More actions

   This label was auto-applied by github-actions. This is a genuine feature request, not a compliance issue. Could a maintainer please remove
   eeds:compliance\ and add \enhancement\ / \discussion\ instead? Thanks.
5. yash-desai-naik

   changed the title [-]Non-blocking background timer / async ping[/-] [+][FEATURE]: Non-blocking background timer / async ping[/+] on Jun 8, 2026
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Jun 8, 2026
7. yash-desai-naik commented on Jun 8, 2026

   

   yash-desai-naik

   on Jun 8, 2026

   Author

   More actions

   Update: This IS achievable via plugins

   Turns out my original analysis was wrong about the architectural limitation. The plugin opencode-background-agents by kdcokenny works correctly — it fires a background task via delegate() that returns immediately, and the completion notification injects into the chat independently without blocking.

   Tested successfully

   1. Installed opencode-background-agents plugin
   2. Restarted opencode
   3. Used delegate(prompt: "wait 15 seconds then say ping!", agent: "general")
   4. Continued chatting freely — no queueing
   5. Ping arrived ~15s later as an independent message

   What is the actual gap then?

   Not architectural — it is agent awareness. The plugin exposes delegate() / delegation_read() / delegation_list() tools, but the agent won't use them unless prompted to. The user has to explicitly instruct the agent to call delegate().

   What would still help

   A native solution (instead of a plugin) could:

   • Make the task tool support a background: true flag natively
   • Give opencode itself built-in awareness of background delegation so it proactively uses the pattern
   • Avoid needing to install and configure a third-party plugin

   But the core async non-blocking ping use case is solved by the existing plugin ecosystem. Closing this as "works via plugins" might make sense, unless the request is specifically for a built-in first-class solution.
8. rekram1-node commented on Jun 8, 2026

   

   rekram1-node

   on Jun 8, 2026

   Collaborator

   More actions

   AUTOMATED: closing as duplicate of: #5887
9. rekram1-node

   closed this as a duplicateof [feat] True Async/Background Sub-Agent Delegation #5887 on Jun 8, 2026