Approvals & ChangePlans

Anyy separates deciding what to do from authorizing protected effects. An approval is your decision. A ChangePlan is the structured description used for higher-risk state changes.

When Anyy Asks

Authorization can appear for:

• a protected tool call, such as a runtime or desktop action;
• MCP, Skill, Tool, or capability configuration;
• credential-sensitive work;
• external delivery or state changes; or
• a ChangePlan that modifies local or external state.

Read-only work can run directly when tool governance permits it. Effective policy comes from the tool descriptor, Profile configuration, runtime safeguards, and current session mode.

Review Requests in Dashboard

Dashboard offers two review locations:

• Chat shows authorization that belongs to the active execution, including every decision offered by the runtime.
• Approvals provides a Profile-wide queue for Dashboard configuration requests plus recent decision history.

Each pending card can show the operation, summary, source, category, risk, and creation time. Use All, MCP, Skills, or Tools filters to narrow the queue. The central page intentionally offers only Approve or Reject for open items.

History shows the decision, time, actor, source/category, and reason when available. Both pending requests and history change when you switch Profiles.

Approval Decisions

The exact choices depend on the request and surface:

Decision	Effect
Approve / Allow once	Authorize this specific request
Allow for session	Authorize a displayed class of similar operations for this session, when offered
Deny / Reject	Refuse the request; Anyy may revise the approach or stop
Force approve	Exceptional force path shown only when supported

An Allow for session grant is limited to its displayed tool, operation, target, effect, and exclusions. It is not blanket permission for the session.

Before approving, confirm:

1. You asked for this outcome.
2. The path, command, recipient, account, or external target is exact.
3. The effect is no broader than necessary.
4. Credentials and private data go only where intended.
5. Validation would prove the desired outcome.
6. Rollback covers the actual effect when reversal is possible.

Reject unexpected, stale, or unclear requests and ask Anyy for a narrower explanation or plan.

Approval authorizes an effect

It is not an acknowledgement dialog. Approval can permit file changes, commands, configuration updates, external tool calls, or outbound delivery. Read each request before deciding.

What a ChangePlan Contains

A ChangePlan can include:

• reason and risk class;
• current state and proposed changes;
• exact commands or affected services;
• preconditions and expected impact;
• validation steps;
• rollback steps and rollback mode; and
• expiry and approval route.

Approved plans are hash-bound to the reviewed content. If the plan changes, stale approval cannot silently authorize the new version.

Approval Mode and yolo

Sessions and scheduled jobs use one of two execution modes:

• approval — protected actions pause for a decision;
• yolo — approvable actions may continue unattended.

yolo does not remove every safeguard. Anyy still blocks recognized absolute-catastrophe operations, and analysis failures are not treated as approval. It does remove the normal human review step for many consequential actions.

Use yolo only in a bounded, trusted environment

Confirm the task, tools, working directory, external accounts, recipients, and possible effects first. Prefer approval mode for messages, credentials, deletion, or systems outside the Profile.

Change the mode in Dashboard Chat or in the TUI:

/yolo on
/yolo off

Each Cron job has its own execution-mode setting. Yolo is not a bulk-approval command and does not clear an existing queue.

Expiry and Recovery

Approvals and ChangePlans can expire. If a pending request no longer matches current state or cannot be approved, reject it and retry the operation so Anyy produces a fresh request.

An ordinary protected tool approval is valid for 10 minutes. A ChangePlan shows its own expiry, which can be extended when a scheduled operation must remain valid until its due time. Ordinary clarification questions have no default expiry; they remain open until answered, interrupted, or otherwise resolved.

If an approved operation fails, inspect its conversation or tool result, ChangePlan state, and decision history. “Approved” proves authorization—not successful execution or verification.

Tips

• Approve the effect, not merely the assistant's explanation.
• Prefer one-time approval unless a narrow session grant is genuinely repetitive.
• Treat force paths as exceptional.
• Review scheduled yolo jobs periodically.
• Keep backups appropriate to the consequence of the action.

Troubleshooting

Problem	Fix
An expected request is missing	Verify the active Profile and open the session where the operation was proposed
Approve or Reject fails	Reload, run anyy status, and confirm that the request is still open
Execution remains suspended	Look for another approval or clarification in the same session
Request looks unfamiliar	Reject it, inspect the source session and audit context, and rotate credentials if exposure is suspected
Approved work failed	Inspect execution output and validation; approval does not imply success

Configuration changes commonly originate from Tools & Toolsets, MCP Integration, Skills System, and Scheduled Automations.