Template
Agent Settings
Durable controls for autonomy, approvals, notifications, and memory boundaries.
FieldSwitchEffective Policy Preview
Use
Workflow Guidance
Use when behavior should persist across sessions instead of relying on one-off prompts.
Human Control
Users or admins set the boundaries once and review risky changes.
What Can Fail
Settings are hidden, labels are not clickable, or dangerous toggles apply instantly.
Recovery Behavior
Use confirmation, undo, and audit trail for risky setting changes.
State Matrix
Required States
A template is only useful when it shows normal, blocked, and recovery states.
State Coverage
Default
User sees
Recommended policy and why it exists.
System does
Applies safe defaults.
Changed
User sees
New policy, scope, and affected actions.
System does
Records the setting change.
Risky
User sees
Confirmation with impact and rollback.
System does
Waits for explicit confirmation.
| State | User Sees | System Does |
|---|---|---|
| Default | Recommended policy and why it exists. | Applies safe defaults. |
| Changed | New policy, scope, and affected actions. | Records the setting change. |
| Risky | Confirmation with impact and rollback. | Waits for explicit confirmation. |
Implementation
Pattern Pieces
Templates are guidance; registry items stay smaller so teams can compose them into their own product surface.
Field
Stock shadcn/ui field wrapper pairing a label, control, and description.
Switch
Stock shadcn/ui switch used for boolean policy toggles.
Effective Policy Preview
A compact settings summary showing the agent policy currently produced by autonomy, approval, notification, and memory controls.
| Element | Spec |
|---|---|
| Field | Stock shadcn/ui field wrapper pairing a label, control, and description. |
| Switch | Stock shadcn/ui switch used for boolean policy toggles. |
| Effective Policy Preview | A compact settings summary showing the agent policy currently produced by autonomy, approval, notification, and memory controls. |
Build Rules
- ApprovalRisky external actions use a Decision Surface before execution.
- ProvenanceSources, memory, cost, and owner metadata stay visible at the decision point.
- RecoveryBlocked states expose the next input needed instead of showing indefinite activity.