> Documentation index: https://rift.sh/llms.txt

[Use Rift with your agent](https://rift.sh/docs/use-with.md)

# Use Rift with Sprites

A Sprite runs the code and Rift keeps the files. Rift runs on Linux, which is what a Sprite runs.

## Set it up

On your own machine, make an invite for the Sprite.

```
$ rift invite sprite
```

A Sprite keeps its disk, so install Rift and join once, inside the Sprite, with the token the invite printed.

```
$ curl -fsSL https://rift.sh/install | sh
$ rift init --invite <token>
```

Then share the folder it should write to, and have the agent keep its work in that folder, which appears in the Sprite at `~/rift/sprite-1`.

```
# your machine
$ rift share runs/sprite-1 sprite
```

## What you get

Files the agent writes there reach your machines as they are written. A Sprite pauses about 30 seconds after activity stops, and sync stops with it. After a cold wake its processes start fresh, so run `rift status` on waking, or register Rift as a service on the Sprite.

Written from Fly.io's page on the [Sprite lifecycle](https://docs.fly.io/sprites/concepts/lifecycle), read in October 2026.

## How they differ

The comparison says what each one does, who can read your files and when to choose which.

[Rift vs Sprites](https://rift.sh/compare/rift-vs-sprites.md)