Skip to content
OneviumDocs
On this page

Choose a work mode and permission profile

Understand Code/Plan and Default/Auto/Full Access, set new-session defaults, and verify actual execution.

Two choices with different jobs#

Code/Plan controls how work progresses. Default/Auto/Full Access controls how tool permissions are handled. You can review an approach in Plan, then keep an appropriate permission profile when implementing it.

Choose the work mode#

ModeWhen to use itWhat to do
CodeThe goal and scope are clear and work should executeSupply the goal, allowed changes, and verification requirements
PlanUnderstand the current state, compare approaches, or review impact firstSwitch to Plan in the composer, request an approach, and review it before implementation

Plan is not a third permission profile. Auto or Full Access does not mean every implementation detail is already approved when you choose Plan. Code does not mean unlimited access either.

Choose tool permissions#

ProfileUseful forActual behavior and limits
DefaultA new project or work where you want to review permission requestsRequests requiring confirmation use approval cards; rules, tools, and SDK behavior still apply, so not every call must prompt
AutoReducing repeated confirmation during routine developmentThe SDK classifier handles requests; decisions needing a person can still return to approval
Full AccessContinuous, explicitly authorized work in a trusted environmentReduces ordinary tool approvals; does not grant external account access or replace Plan review, necessary questions, or verification

Define project, file, and account scope first. Prompts describe the intended work; tool authorization and account permissions determine what can actually succeed.

Session choices and global defaults#

  • This task: change the permission selector in the conversation's input area.
  • Future tasks: open Settings → General → Default Permission Mode, choose the starting profile, then create a new conversation to check it.
  • Reasoning effort: Settings → AI services → the relevant connection’s Manage Models → Default reasoning effort sets the starting level for new conversations by model. This controls reasoning effort, not authorization.

Existing conversations can keep overrides. The fresh-install baseline is Full Access, while older configurations may differ. Use the displayed value; the option named Default is not necessarily the installation default.

First exercise: plan, then make a small change#

  1. Open a demo project and inspect its directory and existing changes.
  2. Choose Plan and an appropriate permission profile, then send:
text
Plan a clearer empty state for the member list.
Read the component and project conventions first.
Identify affected files, loading/empty/error states, and checks.
Do not edit until the approach is approved.
  1. Review the plan's coverage and boundaries, then allow implementation.
  2. When an approval card appears, inspect the action, arguments, files, and target service before approving.
  3. Review the diff and perform the agreed checks.

Confirm the controls worked#

The new conversation shows the expected profile, Plan produced a reviewable approach, and tool records and changes stay within scope. The final diff, tests, or page behavior should demonstrate completion.

No approval card does not automatically mean the setting failed: rules or the classifier may already handle a call. A denial does not automatically justify Full Access either; inspect the reason and required access first.

Automations and external entry points#

The current automation create/edit form has no Default/Auto selector; tasks created through it use Full Access. They do not wait for ordinary per-step conversation approval and should not be described as inheriting the current chat's profile. Test the prompt in a demo project before scheduling it.

Channel bots have their own approval policies. External access uses assistant bindings and authorization. Changing a local conversation's profile does not automatically change these entry points.

Common problems#

  • Default changed but old chat did not: it applies to future sessions; inspect the old session's own value.
  • Task remains waiting: locate the approval or question and respond to it rather than repeatedly saying “continue.”
  • Work exceeds scope: stop and clarify the task instead of first expanding permissions.
  • Different terminology: CLI permissionMode and chat modes use different values; do not copy them interchangeably.

Waiting times and unanswered requests

Open Settings → Permissions and confirmations and choose the relevant category. Ordinary confirmations with no saved new rule wait 30 seconds, then confirm. Questions wait two minutes, then use an available default option; required free-text content is never fabricated. Set a different wait or denial behavior if your task needs it, and check the countdown on the next request.

Existing vault timeout-denial preferences continue to cover vault, SSH and sensitive actions. Source checks and channel sender allowlists still apply. A channel configured for Full access executes admitted messages without ordinary confirmation; changing a desktop conversation does not change that channel's policy.

Next steps#

Use the settings reference for defaults, projects and sessions for scope, and files and Review to verify results.