Check the selected access mode
Access mode sets how a mission handles permission requests. The composer shows the current choice. Work mode and access mode are separate controls.
The four modes
| Mode | What it permits |
|---|---|
| Ask for approval | Commands and edits wait for a decision through the supported approval path. |
| Auto-accept edits | Working-copy edits can apply; commands still wait for approval. |
| Sandboxed access | Workspace commands and edits can run within the enforced boundary; host and connected writes stay constrained. |
| Full access | Host files, processes, network and connected tools can run without permission prompts. |
External coding agents differ in which operations they report for approval. Read-only operations may proceed without a prompt. Full access removes permission prompts within the allowed runtime; it does not override a service's authorization, an account limit or a Skyflo Cloud Git restriction.
Review the actual request
Read the command or change, its affected paths, and the reason it stopped. Approve only the action you intend. Declining lets you give a different instruction. If the action changes or the request expires, the mission must present a current request.
Plan approval and action approval have different scopes. A plan describes intended work; an action request binds a particular effect.
Skyflo Cloud
A mission in Skyflo Cloud runs with Full access inside its own machine. Its GitHub actions remain restricted to the mission's branch. A moved mission returns to the access setting it had on the Mac. Review the move dialog's access and data-sharing facts before moving it.