Skip to content

Fyle for developersRun any agent in a folder. Review what it changed before it lands.

Coding agents are good at changing files. Fyle is a cloud file system that mounts like any folder, so cd ~/Fyle/project && claude just works, and fyle agent gives each run its own session with a change summary, landing rules and review.

Create an accountSee an agent at work

Agents write fast; shared files need guard rails

Git covers your code. It doesn’t cover the docs, data, designs and generated files that live next to it on a shared drive, where an agent’s write simply replaces what was there.

Remote agents need file access too, ideally through the same permissions as the desktop, not a separate API with its own rules.

How Fyle fits

Fyle is in development. This is what exists today and what is planned, marked on every line.

Available now

  • Device sign-in for the desktop app and CLI: approve a short code in the browser, with no password typed into a terminal.Available now
  • Two-factor sign-in with an authenticator app, which an organisation can require for everyone.Available now

Planned

  • A Linux FUSE mount, macOS File Provider and Windows Cloud Files; files hydrate on demand and are cached.Planned: desktop launch
  • fyle agent claude or fyle agent -- codex runs the agent in a session folder: an overlay where reads fall through to the workspace and writes stay in the session.Planned: agent layer
  • On exit, changes on current files land and stale ones become branches; fyle agent ls | show | land | discard manage sessions.Planned: agent layer
  • MCP server (stdio and streamable HTTP), a CLI, a public API and TypeScript and Rust SDKs.Planned: agent layer
  • Text, code and Markdown get diffs and three-way merge in review.Planned: review

An agent at work

The agent edits three reference pages and adds a migration note. A teammate changed one of the pages during the session, so that edit becomes a branch with a three-way merge offered in review.

$ cd ~/Fyle/acme/docs-site
$ fyle agent claude --task "Update the API reference pages for the new pagination parameters"

Session ended · 4 changes
  reference/list-entries.md       modified
  reference/changes.md            modified
  guides/pagination-migration.md  new
  reference/search.md             branched (a teammate edited it during the session)
3 files landed. 1 branch waiting for review.
Illustration of a planned workflow. Names are examples; commands and output may change before release.

Credentials and access

  • Agents get scoped, short-lived credentials, never your session; MCP has no privileged bypass of the permissions people have.
  • File bytes go directly between your machine and object storage over short-lived presigned requests; storage keys never ship in the client.
  • Device sign-in uses a code you approve in the browser, and it is available now.

Not legal advice. Fyle features mentioned here are planned unless marked available now.

Try Fyle when the drive is ready.

Create an account

Sources

Last checked: . Regulatory points link to the regulator’s own guidance. Competitor facts live on the comparison pages, each with its sources.

  1. 1.Fyle vs Archil (sourced comparison)/compare/fyle-vs-archil
  2. 2.Fyle vs Mesa (sourced comparison)/compare/fyle-vs-mesa
  3. 3.Fyle vs rclone (sourced comparison)/compare/fyle-vs-rclone