Know which file you are using
- App data
- Records and files maintained by an app on the host.
- Uploaded attachment
- File contents sent with a message for the task.
- Local file reference
- A reference to an existing host file. Changes to that file affect the original.
- Artifact
- A file published as a result of an Agent session.
Saving an artifact to another location creates a separate file unless the action explicitly updates an existing destination. Source Snapshots are described under Build and improve.
Choose file and folder access
An app can request access to a file or folder through platform controls. Read the requested path and whether the app needs to read or write it. Grant access to the location needed for the task.
In Remote Access, host file pickers refer to the computer or server running AppJuice. A browser upload is the way to send a file from the device you are holding. These are different sources.
App permissions and Agent modes
App permissions govern system capabilities available to the app. Agent permission settings govern its managed tool actions. An operating-system permission, such as Screen Recording, is a further requirement where applicable.
Strict and Relaxed change how Agent actions are reviewed and approved. Relaxed does not remove the sandbox or allow every action. Hard policy denials remain blocked.
Read the execution boundary
- Sandbox
- The action uses AppJuice's restricted execution environment.
- Extra folder access
- The action requests specified paths while remaining within a sandbox.
- Outside-sandbox access
- The action requests execution beyond that sandbox. Review the reason and scope carefully.
The available enforcement depends on the operating system and deployment. In a server or container installation, access is to the host or mounted storage made available there.
Understand reviews and approvals
Auto Review assesses actions that require review. Depending on the mode and request, the result can be an automatic decision or a request for your approval. The activity details show the decision and its reason.
A requested permission describes what the Agent asked for; it is not proof that the action ran with that access. Blocked by policy and Not run mean the rejected action was not executed. An execution error after a command starts can still leave partial output or changes.
If an action is blocked, read the reason and ask the Agent to explain what needs to change. You may be able to choose a different folder or complete the task with less access.
Understand where data goes
Apps and their runtime data are local by default. When a task calls a cloud model or third-party service, that service receives the request content needed for the operation. This can include prompts, attachments, conversation context, or tool results.
Local model inference can keep the model request on the host. Other tools may still access the internet. Review the app's workflow and configured services before using material that must stay on a particular device.