# Install

> One command and one GitHub sign-in. From then on your agent keeps files in flie.

flie is a filesystem in the cloud for you and your agents: folders and files owned by your
account, private until you share them. An agent reaches it by two routes, and both reach the
same account. [Over MCP](https://flie.sh/docs/connect.md), a host registers the server by its URL and nothing is
installed. The `flie` command adds the one thing MCP has not: sending a file from this machine
and writing one back to it.

### 1. Install the command

```sh
curl -fsSL 'https://flie.sh/install.sh' | sh
```

It installs the native command to `~/.local/bin/flie`, without sudo and without Node or npm.
macOS on Apple Silicon only. The installer verifies the release checksum before it replaces an
existing executable, and saves this server, so signing in takes no flags.

It changes no shell startup file. If `~/.local/bin` is not on your PATH, it prints the one line
that adds it for the current terminal.

### 2. Sign in

```sh
flie login
```

It opens GitHub in your browser on this machine and waits until you have signed in. The
sign-in lasts 30 days.

### 3. Give your agent the skill

```sh
flie skill install --agent claude
```

For Codex or Cursor, use `codex` or `cursor` in place of `claude`. Reload the agent so the skill
loads. The installer never installs a skill itself.

## Let your agent do it

Paste this to your coding agent:

```text
1. Run: curl -fsSL 'https://flie.sh/install.sh' | sh
2. Ensure `flie` resolves in a new shell; if it does not, add ~/.local/bin to PATH in the shell startup file and report the change you made.
3. Run: flie login; it prints a link and waits. Give that link to the person to open in their browser on this laptop — do not fetch it yourself — and keep the command waiting until it prints Signed in.
4. Run: flie skill install --agent codex|claude|cursor, choosing the one that names your own harness, then reload yourself so the flie skill loads.
```

It is the only reader that may edit your shell startup file, and it tells you when it does.

## Update and remove

Run the install command again to update or reinstall. Your sign-in and settings are kept.

`rm ~/.local/bin/flie` removes the command. Your account and its files stay on the server, and
signing in again with the same GitHub identity returns to them.

The binary is not Developer ID signed or notarized. The checksum checks that the download is
intact, not who published it. The installer never disables Gatekeeper or removes quarantine.
[Read the installer](https://flie.sh/install.sh) before running it.
