-
-
-
@servicedesk why we need to add opencode specific option in task automation setting if environment is sufficient in this case?
-
@robin Good point — Environment Variables are already sufficient functionally. Setting
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueon the workspace spec applies to the whole process tree (including sub-agents). The dedicated checkbox was proposed mainly for discoverability: users following the template /--dangerously-skip-permissionspattern may not realize the CLI flag does not carry to sub-agents, and the original request in issue #2934 asked for a contextual control with that hint.If you prefer not to add an Open Code-specific Task Automation option, we can drop that part. Possible reduced scopes:
- Close this issue — rely on Environment Variables only (workaround already works today)
- Templates only — add
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueto built-in Open Code shell/container templates by default (matches existing--dangerously-skip-permissionsintent for sub-agents), but no new checkbox - Keep as specified — checkbox + template defaults as in the acceptance criteria
My recommendation is (2) unless you want zero Open Code-specific productization here. Which do you prefer?
-
Option 2
-
@robin Acknowledged — proceeding with option 2 (templates only).
Reduced scope for this issue:
- Add
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueto built-in Open Code shell and container templates by default - No Task Automation checkbox / Open Code-specific UI option
I do not have permission to write code in this project (
tod issue checkout --for-writereturned HTTP 403), so I cannot implement the template change myself. Please take the implementation from here, or grant write access if you want me to do it. - Add
-
Modify issue description to reflect this
-
Previous Value Current Value Add Task Automation checkbox for Open Code skip-permissions env var
Enable Open Code skip-permissions env var in built-in templates
-
@robin Updated the issue title and description to reflect option 2: templates only, no Task Automation checkbox.
-
Name Previous Value Current Value Assignee
robin
wh
-
-
Implemented templates-only change: built-in Open Code shell and container templates now set
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueby default so sub-agents inherit skip-permissions. No Task Automation checkbox or Open Code-specific UI was added.Please review pr #105.
-
Happy with all this @robin
Thank you.
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Summary
Add
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueto built-in Open Code shell and container templates by default so sub-agents inherit skip-permissions.Background
Raised from issue #2934. Open Code workspace templates already run tasks as:
The CLI flag does not carry to sub-agents; the env var does. Workspace specs already support Environment Variables, so setting
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=truemanually works today.Scope (agreed)
Templates only — no Task Automation checkbox / Open Code-specific UI option.
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueto built-in Open Code shell and container templates by defaultAcceptance criteria
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueenabled by defaultWorkaround for existing specs
Manually add
OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=trueunder Environment Variables on the workspace spec.