Repository navigation
promptAsync background work can lose request instance context #26526
Description
Description
promptAsync starts prompt work in a forked effect and returns 204 immediately. Because the forked prompt effect does not explicitly provide the request's InstanceRef / WorkspaceRef, later background work can run with the default instance context instead of the request instance.
In integrations that depend on project-specific agent configuration, this can make subagent lookup see only default agents and fail to resolve custom agents.
The streaming prompt route already captures and provides the instance/workspace context around the prompt effect. promptAsync should do the same before forking.
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 9, 2026
This issue might be a duplicate of existing issues. Please check:
promptAsyncfails to find project-specific agents (.opencode/agents/*) because it does not carry the request's instance/workspace context into the forked effect, resulting in only global config being visible.If this is the same issue, please consider closing this one and adding any new details to #21659 instead.
github-actions commentedon Jul 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.