[FEATURE]:Asynchronous user agent communication. #15969

Activity

1. TZubiri

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Mar 4, 2026
2. github-actions

   assigned

   rekram1-node

   on Mar 4, 2026
3. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Mar 4, 2026
4. github-actions commented on Mar 4, 2026

   

   github-actionsBot

   on Mar 4, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • [feat] True Async/Background Sub-Agent Delegation #5887: [feat] True Async/Background Sub-Agent Delegation — same concept of the agent continuing work while able to interact with the user asynchronously
   • Feature Request: Async Task Management - Non-blocking Subagent Dispatch #15069: Feature Request: Async Task Management - Non-blocking Subagent Dispatch — nearly identical request for non-blocking subagent execution with main session remaining interactive
   • Support background tool execution #9462: Support background tool execution — related request for background/async tool execution
5. TZubiri commented on Mar 4, 2026

   

   TZubiri

   on Mar 4, 2026

   Author

   More actions

   #5887
6. TZubiri commented on Mar 4, 2026

   

   TZubiri

   on Mar 4, 2026

   Author

   More actions

   For the scenario described (Agent needs to ask a question).there might be a solution that just uses 2 sessions

   There's 3 distinct properties of each solution by complexity.

   1. Recursiveness: Each session can theoretically spawn other session of the same type as the main session. An example would be the 'subagents' solution.
   2. Arbitrary length sessions: A main session can spawn an unlimited amount of subsessions of a different type. Also some 'subagents' proposals.
   3. Fixed length alternative sessions: At most one additional type of session is added or split. For example a solution where we have a session for the conversation, and another that

   Obviously solutions of the first and second type increase the scope of the project, the complexity and cost of the project.

   An acceptable solution would be of the third type, not adding recursiveness and not adding the capacity to add an arbitrary amount of additional context. If average token per context is increased, it should be an n+1 cost increase.

   A hacky implementation of this (that anyone can try), is asking the model, either via prompt, skill, or AGENTS.md, to communicate through files, either by using a MESSAGES.txt or through comments.

   The issue of this workaround is that the models are not quite trained to follow this instruction. And they usually just don't attempt to communicate or to check communications.
7. thdxr

   removed

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
8. github-actions commented on Jul 5, 2026

   

   github-actionsBot

   on Jul 5, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Jul 5, 2026