Mount Linear, GitHub, Notion, Slack, HubSpot, Salesforce, and your own systems as a realtime filesystem. Agents inspect provider data with bash, write records by saving files, and coordinate through scoped mounts instead of bespoke tool glue.
Relayfile turns the systems where work happens into paths an agent can list, read, grep, edit, and watch.
Mount Linear issues, GitHub PRs, Notion pages, Slack channels, and SaaS records as ordinary paths.
Create, patch, and delete provider records by saving files. Adapters validate changes and queue writeback.
Every writer publishes a new revision so other agents see fresh state on their next read.
Give each agent path-level read, write, watch, or admin permissions instead of broad provider credentials.
Precompute high-value rollups like yesterday.md so agents start with the answer-shaped file.
Agents use cat, grep, find, jq, rg, and editors against a real local mount or the HTTP API.
Provider auth, pagination, sync, and writeback stay behind the mount. The agent sees one workspace tree with layouts, indexes, digests, and provider records side by side.
Vercel AI SDK, Claude Agent SDK, OpenAI Agents SDK, scripts, and terminal-native agents can all read the same workspace tree and write through the same contract.
import { RelayfileSetup } from '@relayfile/sdk';
const setup = new RelayfileSetup({
accessToken: process.env.RELAYFILE_ACCESS_TOKEN!,
});
const handle = await setup.ensureMountedWorkspace({
workspaceId: 'rw_123',
provider: 'notion',
verifyProvider: true,
localDir: '/workspace/relayfile',
});
console.log(handle.env().RELAYFILE_LOCAL_DIR);Purpose-built for agents that need to work across real SaaS systems.
Agents open the files they need instead of loading a large typed tool surface for every connected provider.
Provider updates are file operations with validation, retries, and audit trails handled by the integration layer.
Reviewer, implementer, and orchestrator agents can all mount the same workspace and react to the same revisions.
Connect a provider, read the generated workspace, then write back through the same file interface. The first useful workflow is a directory listing, not a framework migration.
npx relayfile setup \
--provider notion \
--workspace research-room \
--local-dir ./relayfile-mountls ./relayfile-mount
cat ./relayfile-mount/LAYOUT.md
cat ./relayfile-mount/digests/yesterday.mdcat > ./relayfile-mount/linear/issues/drafts/follow-up.json <<'JSON'
{
"title": "Follow up from digest",
"state": "Todo"
}
JSONRelayfile extends the Agent Relay platform with shared storage for agents that communicate, coordinate, and act on the same files.