REMOTE ARC

Apps and account connections

Connect cloud accounts independently of Arc Agent and review each write request.

Connect your own account

Open the App catalog, choose a category or integration, and check its connection availability and supported operations. When configured, Connect your account opens the signed-in Apps page. Choose read access or explicitly add write access. OAuth Apps redirect to the provider's consent screen; API credential Apps instead accept a key or access token from your own provider account. No local computer or Arc Agent is required for cloud App operations.

Discover and use operations

Authorize apps:read for a compatible MCP client. Ask the AI to use list_apps to find a provider, then request that provider's operation schemas. call_app takes the connection ID, operation, arguments and a stable requestId. Discovery is paginated so hundreds of integration schemas do not fill every chat. Remote Arc implements bounded native API actions; a catalog entry does not promise all features of the upstream service.

Review writes and inspect results

A write requires apps:write, write permission on the connection and approval of the exact destination and payload in Apps. Check what will be sent or created before approving. Reuse the same requestId to collect its state. An uncertain external write is not automatically repeated. Provider acknowledgement means the API accepted the request; verify delivery or the final artifact at the provider when needed.

Connection states and rollout

Waiting for configuration means Remote Arc has not supplied this provider's platform credentials or enabled the service. It is different from a disconnected user account. After connecting, revoked or expired credentials may require reconnection. Disconnecting removes the saved credential and blocks pending actions. The initial production release relies on automated protocol checks; real-account workflows are being tried by the owner and are not certified across all providers.