[GH-ISSUE #57] feat: YOLO #23

Closed
opened 2026-10-18 14:02:07 +00:00 by bsakaguchi · 4 comments
Owner

Originally created by @naqerl on GitHub (Jun 15, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/57

It would be great to have YOLO mode toggle even in the global settings, as it is on when using from OpenWebUI, yet in the computer it asks permission for every bash tool call

Originally created by @naqerl on GitHub (Jun 15, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/57 It would be great to have YOLO mode toggle even in the global settings, as it is on when using from OpenWebUI, yet in the computer it asks permission for every bash tool call
Author
Owner

@tjbck commented on GitHub (Jun 16, 2026):

Could you confirm whether you mean exposing the existing remembered Tool permissions -> Full access setting in global Settings, rather than changing the API gateway behavior?

<!-- gh-comment-id:4721363106 --> @tjbck commented on GitHub (Jun 16, 2026): Could you confirm whether you mean exposing the existing remembered Tool permissions -> Full access setting in global Settings, rather than changing the API gateway behavior?
Author
Owner

@naqerl commented on GitHub (Jun 16, 2026):

Yes, this is only about cptr itself independent from the gateway. For the start, it could be locally configured per workspace in .cptr/ as well as globally for the whole instance

<!-- gh-comment-id:4721547168 --> @naqerl commented on GitHub (Jun 16, 2026): Yes, this is only about cptr itself independent from the gateway. For the start, it could be locally configured per workspace in `.cptr/` as well as globally for the whole instance
Author
Owner

@tjbck commented on GitHub (Jun 18, 2026):

Full access already exists and is remembered globally as a user preference from the chat tool permissions menu. API Gateway already forces full access via the gateway. The only missing piece I see is a Settings-page surface and/or a workspace-local .cptr config override, if that’s what this issue is asking for.

@naqerl Could you confirm?

<!-- gh-comment-id:4742102156 --> @tjbck commented on GitHub (Jun 18, 2026): Full access already exists and is remembered globally as a user preference from the chat tool permissions menu. API Gateway already forces full access via the gateway. The only missing piece I see is a Settings-page surface and/or a workspace-local .cptr config override, if that’s what this issue is asking for. @naqerl Could you confirm?
Author
Owner

@naqerl commented on GitHub (Jun 18, 2026):

I've misunderstood your comment about tool permissions, existing behavior is enough and I do not think that the special entry in the global setting is needed after all. Thanks for your time.

<!-- gh-comment-id:4742264659 --> @naqerl commented on GitHub (Jun 18, 2026): I've misunderstood your comment about tool permissions, existing behavior is enough and I do not think that the special entry in the global setting is needed after all. Thanks for your time.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/computer#23
No description provided.