Back to guides

Give every task a clear scope.

Local files, schedules, and chat channels each extend what a task can do. Enable the parts you need and review the results.

Choose a working folder

Use a folder intended for the task and keep backups of files you care about. Task-relevant file content can be sent to the model. Avoid placing unrelated secrets or personal files in the working folder.

Use bounded scripts

Workspace scripts use the bundled Node runtime within the allowed working directory. They are intended for scoped task work, with restrictions on host credentials and child processes. Review generated files before using them elsewhere.

Schedule work on an available host

Set the timing and instructions, check the selected phone and model, and run the task manually once. Keep the computer, app, phone, and required services available. A schedule cannot wake a powered-off computer or guarantee a third-party app’s availability.

Connect an authorized chat

Configure a supported channel, then allow the conversations that may trigger tasks. Keep that allowlist limited to people you trust. Channel access does not automatically grant local file access. The first Microsoft Store release excludes WhatsApp.

Review remote access

Remote phone sharing uses the signaling service you configure and a peer-to-peer media connection. Network restrictions can prevent a connection. Use trusted peers and keep access credentials private.

Clean up after a task

Stop active work and disconnect channels before deleting local data. Use the data settings to clear history, screenshots, or logs; exported files and backups need to be managed separately.