Authorization needs a target and scope

Deletion, overwriting, bulk reference replacement and discarding unsaved changes can be hard to recover from. A confirmation should identify the objects, impact and known recovery conditions. Ordinary work uses the task authorization already given, without requiring users to read every line of C#.

Dismissal, refusal, cancellation, timeout and disconnection are never consent. A denied dangerous action must not be retried through another tool.

Intent is not a safety proof

A one-sentence explanation helps users understand the plan. It remains distinct from the code, target and actual outcome. A model reporting low risk or passing a static check does not prove an arbitrary script safe.

Chippo retains arbitrary C# execution with COM and .NET access. It cannot promise a complete sandbox or unbypassable file permission isolation. Treat it as a trusted local assistant and read the limitations.