If you want Notion, Slack, Linear, GitHub, or other provider-backed files without running any infrastructure, use Hosted Agent Relay. Agent Relay Cloud runs the workspace, the Relayfile API, scoped auth, Nango OAuth, provider sync workers, and writeback workers for you. There is no integration runtime or token configuration on your machine.
The setup flow
From the project where your agent will work:
npx relayfile@latestRelayfile completes Google sign-in, automatically creates the account and workspace without an invite code, connects GitHub, and mounts at ./relayfile-mount. The local directory is just the agent's file interface — the integration stack is hosted. Re-running the same command reuses the workspace, refreshes the session, and skips provider connection when GitHub is already connected.
Use npx relayfile@latest setup --provider notion --workspace my-agent --local-dir ./relayfile-mount for another provider or explicit names. --no-open prints hosted login and connect URLs instead of opening a browser.
After setup, hand the agent the mount path and it reads and writes under $RELAYFILE_LOCAL_DIR/<provider>/... instead of calling provider APIs directly:
export RELAYFILE_LOCAL_DIR="$PWD/relayfile-mount"For the programmatic equivalent from inside an authorized sandbox, see Mounting from a sandbox.
What Cloud manages
Cloud runs the whole integration path so you don't operate the stack:
- Managed OAuth (Nango). The polished connect-session flow and provider credentials.
- Provider sync workers. Initial backfill plus live webhook ingestion, normalized into the file tree.
- Writeback workers. Your agents' file writes turned into provider API calls, with retry and dead-letter handling.
- Scoped auth. Short-lived, path-scoped Relayfile tokens minted per workspace and per agent.
Local OSS vs Hosted
Use local OSS for development, tests, or fully self-hosted deployments. Use Hosted Agent Relay when you want provider-backed files to work without operating the stack.
| Need | Local OSS | Hosted Agent Relay |
|---|---|---|
| Run the Relayfile API | you run it | managed |
| Mount files for an agent | yes | yes |
| Issue scoped tokens | run relayauth or equivalent | managed |
| Provider OAuth | self-host provider auth | managed |
| Provider sync / writeback | self-host workers | managed |
| Nango | self-host for end-to-end OAuth | managed |
For end-to-end self-hosting, run relayfile, relayauth, the relevant adapters and providers, and Nango. The split is deliberate: Relayfile's OSS surface handles the VFS, scoped tokens, generic ingest, writeback queue, and mount; the polished OAuth connect flow and provider sync definitions are hosted by Cloud or implemented in your self-host provider stack.
Relayfile itself never stores third-party OAuth credentials. Whether hosted or self-hosted, credentials live in the provider layer (Nango, Composio, Pipedream) — Relayfile receives normalized files, events, writeback operations, and a connectionId.
file.agentrelay.com
relayfile-cloud is the standalone Cloudflare service for the hosted Relayfile data plane, currently being extracted from the internal SST monorepo and moved onto the file.agentrelay.com domain. It's a rebuild in progress: the previous standalone implementation has been archived (not deleted) under the git tag archive/standalone-impl-pre-migration, and the source of truth being ported from is the internal cloud monorepo's packages/relayfile and infra/relayfile.ts. The control plane today resolves through agentrelay.com/cloud; the data plane is being consolidated onto its own domain as part of that migration.