Provider requests go to the selected provider
Codex or Claude receives the task data needed for the coding workflow you start.
Local-first AI agent supervision
Your repositories and provider credentials stay on your computer.
Asyncly runs as a desktop supervisor around local workspaces and coding-agent tools. Account, licensing, releases, support, and services you explicitly choose have narrower network roles.
Data boundary
Know which system handles each part of the workflow.
Local-first does not mean the app never uses a network. It means repositories, credentials, and complete workspace state are not uploaded to Asyncly by default.
On your computer
The desktop app keeps the complete local operating context.
Repository contents and pathsProvider credentialsWorkspace configurationTask and thread historyLocal diagnosticsVisual capturesConnected services
Network services receive the data needed for the function you choose.
Account and sign-in stateTrial and license stateRelease availabilitySupport messages you sendSelected provider requestsExplicitly connected workflowsPlain limits
Local work can still call the services needed to complete it.
The provider you select handles coding-agent requests under that provider's account and privacy terms. Asyncly services handle the parts of the product that require an account, entitlement, release, relay, or support function.
Product metrics exclude prompt and source content
The metrics channel can report counts and performance facts. It does not send prompt text, responses, source files, file paths, attachments, or provider credentials.
Support receives what you choose to share
Messages, logs, screenshots, or attachments leave your computer when you deliberately send them for support.
Mobile supervision has its own boundary
A connected phone receives reduced workspace and task state. The privacy policy explains direct-device and hosted-relay behavior in detail.
Review the full policy