How it works
Choose your folder access
During device enrollment, select allowed folders. The recommended Standard profile grants read and write inside those folders; it is not read-only.
Keep sensitive operations disabled
Terminal, Docker and deletion require separate permissions. Terminal commands run as the local OS account and are not sandboxed by the file folder list.
Configure approvals and blocked operations
Command/operation policies include deny_dangerous, ask_for_dangerous, ask_for_sensitive and custom restrictions. An action can return APPROVAL_REQUIRED; approvals expire and are bound to the request.
Review and revoke access
Review device and activity information in your dashboard and revoke devices or access when they are no longer needed.
Where data flows
Original files remain on the enrolled computer, but requested content and tool results can transit the RemoteCommand relay to the AI provider you have connected. Review the provider's data handling policies too.
No blanket security claims
Use account security controls, narrow OS permissions and local command policies. This page does not claim independent certifications, zero-knowledge processing, full terminal sandboxing or a particular SLA.
Frequently asked questions
Is every new device read-only by default?
No. The documented recommended Standard profile permits read/write within selected folders; terminal, Docker and deletion remain disabled unless separately allowed.
Does an approval make a command guaranteed to execute?
No. An approval may permit a retry, but local restrictions and runtime errors still apply.