Repository navigation
[FEATURE]: GitLab Duo Workflow Service tool-call approval integration #19958
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
When using GitLab's Duo Workflow Service (DWS) as the AI backend, DWS can request approval before executing sensitive tools (e.g. run_command, create_commit). Currently opencode has no mechanism to surface this approval checkpoint to the user — the session either silently fails or hangs indefinitely.
Proposed solution: Wire the DWS approval-required event into opencode's existing permission system so users see the standard permission prompt when DWS requires approval.
- Set
sessionPreapprovedToolsfrom the agent/session permission ruleset so tools without an explicitaskrule are pre-approved (preserving current behaviour) - Delegate
approvalHandlertoPermission.askwith aworkflow_tool_approvalpermission type - Support "Allow always" to extend pre-approvals for the session
- Forward rejection decisions back to DWS so the workflow closes cleanly
Activity
github-actions commentedon Mar 29, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:and include the required verification checkbox confirming the feature doesn't already exist.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
If you believe this was flagged incorrectly, please let a maintainer know.
[-]feat: GitLab Duo Workflow Service tool-call approval integration[/-][+][FEATURE]: GitLab Duo Workflow Service tool-call approval integration[/+]github-actions commentedon Mar 29, 2026
Thank you for updating the issue! It now follows the contributing guidelines and has been marked as compliant.