Approval Flow
Overview
This page explains why some actions require approval when Ghast AI is used remotely, and how ordinary users should understand that flow.
Why the remote path requires approvals
Remote control is not the same thing as moving the sidebar unchanged into another channel. Once a remote entry point participates in product use, the system needs to preserve confirmation steps for more sensitive actions.
For most users, the meaning of the approval flow is direct: when something needs more caution, the system does not automatically execute every action without confirmation.
What this flow means for users
It mainly provides three safeguards:
- Remote actions are not executed with unlimited freedom by default.
- Some more sensitive actions require another confirmation or are handled more cautiously.
- Remote use keeps its own boundary instead of becoming identical to direct local operation.
What to expect in normal use
If remote control is already enabled, the following should be treated as normal:
- Some actions do not complete in a single step.
- Remote use may not feel exactly the same as direct use in the sidebar.
- When the system asks for confirmation, that is boundary control first, not proof that the setup failed.
A steadier way to use it
For ordinary users, the more reliable approach is:
- Enable remote control only when it is genuinely needed.
- Start by using simple, lower-risk remote actions to confirm that the channel is live.
- Treat "more sensitive actions may require approval" as a normal part of the remote path.
Ghast AI's current remote approval flow exists to preserve necessary confirmation steps when a remote entry point is in use. For most users, its purpose is not to add complexity but to keep a clear boundary around more sensitive remote actions.