Preferences control how the operator works with you. They help you choose an approach to planning, execution, model use, and interaction without repeating those choices in every message.
Choose an approach
For unfamiliar or consequential work, begin with a plan and review it before execution. For a well-understood task, direct execution can reduce back-and-forth. Approval preferences determine which actions require review within the controls available to that resource.
| Choice | Purpose |
|---|---|
| Plan first | Scope, approach, or consequences need agreement. |
| Execute the task | The desired result and boundaries are already clear. |
| Review critical actions | Routine work can proceed, but consequential changes need attention. |
| Review all changes | You want to inspect changes before they happen. |
An execution preference never grants access to another person's resource or bypasses platform restrictions. A model choice also does not authorize a connected account.
Use the Composer controls
Open the relevant control directly or choose it from the slash command menu.
| Control | Decision | Guide |
|---|---|---|
/model | Use Auto or choose an available model | Model selection |
/permission | Which actions need approval under the available policy | Permissions |
/plan | Whether to establish an approach before execution | Plans |
/steer | How to deliver another message while work is running | Queue or steer |
Permission choices include Autonomous, Critical actions, and All actions where supported. They govern review within the current authorization boundary; Autonomous does not give the Operator unrestricted access. Read the control's scope before changing it, especially in a shared Workspace or Agent.
Planning and approval solve different problems. A plan helps establish what should happen. Approval controls determine when an action needs your review. Enabling Plan mode does not approve the resulting Plan.
Example: explore before changing
Suppose you want to reorganize a customer portal, but have not settled on its navigation.
- Enable Plan mode from
/plan. - Describe the audience, existing structure, and desired improvement.
- Review the proposed approach and clarify unresolved choices.
- Approve the intended Plan revision when you are ready to proceed.
For a later, well-defined correction, such as adjusting one label, you may prefer direct execution within the same access and approval constraints. Choose according to the task rather than maintaining a permanent instruction to plan every small change.
Example: guide work already underway
If a draft is heading in the wrong direction, use steering to give timely guidance: “Keep the customer examples, but shorten the technical explanation.” If the request should happen afterward, queue it instead: “After this draft, create a three-sentence summary.” See Messaging for delivery behavior and stopping work.
These messages guide the current task. Save a preference or instruction only when you want the choice to shape future work too.
Apply preferences at their owner
Use Workspace Preferences for eligible Chat defaults. Review an Agent's own configuration for specialist work, or a Project's settings for development. A Chat does not have a separate library of persistent operator configuration.
Before changing a shared default:
- Confirm the active Workspace or resource.
- Identify which future work should use the change.
- Save the choice and try a small representative task.
- Compare the result with your intent before applying it more broadly.
Changes guide future runs; do not assume a running task has acquired newly selected capabilities. Give task-specific direction in the conversation, and use Instructions for guidance that should persist.