Before you start
- A Sprites account. Sign up at sprites.dev with your Fly.io account and add a card to your organization (new organizations get trial credit). The Sprite is yours: Fly.io bills you directly.
- A Sprites token. Make one at sprites.dev/account. If you’ve
signed in with the
spriteCLI on this computer, Rakumux can use its token instead.
Run a session on your Sprite
1
Turn on the Sprite for a folder
In Rakumux mode, press
N (or click ☁ Sprite at the right of + New session). New sessions
in the current folder now run on your Sprite; N again brings them back to this machine.2
Start a session
Press
n. The first time, Rakumux asks for your Sprites token (or offers the one it found),
then sets the Sprite up, showing each step: it creates a Sprite named rakumux, installs
Rakumux there and connects. After that, n starts a session there in about a second.3
Work in it
The session has
☁ before its name and is listed under the folder you started it from. Going
in is its live terminal on the Sprite. It runs in a folder of the same name in the Sprite’s
home folder, and for a git repository git clone <origin> . is typed there for you to run.
Sign in to your agents on the Sprite the first time.In the Agent feed
Sign in to your Rakumux account (rakumux account login) before you connect the Sprite, and with
the Agent feed on, its sessions take part like this machine’s: what their agents
say, their chats and the Sprite’s sessions show on rakumux.com under the Sprite’s name. When you
connect, Rakumux asks whether replies you write on rakumux.com, or in the feed here, should be typed
into the Sprite’s agents. A reply to a paused Sprite wakes it.
The Sprite never gets your sign-in. It gets a credential of its own that reaches only what a machine
does in the feed: it can’t read your other machines’ chats or change your settings. Revoke it under
Features on rakumux.com, or with rakumux sprite disconnect; it stops working within 15
minutes. Signed out when you connected? Sign in and run rakumux sprite connect again.
Pausing
A Sprite pauses about 30 seconds after the last connection to it closes, freezing whatever runs there. Rakumux keeps it running while an agent works in one of its sessions, so a long task finishes with your laptop closed; once no agent is working, it lets the Sprite pause. Open one of its sessions and the Sprite wakes in about a second. After a long pause its programs stop; Rakumux brings the sessions back with their agents in the same conversation. Other programs, a dev server say, don’t keep it running on their own.Good to know
- Where it runs. Fly.io places Sprites itself; there’s no region to choose. From far away (Australia, say) typing has a noticeable delay. A Fly Machine can run in the region nearest you.
- Cost. Sprites charge for CPU and memory while running and for the storage you use, and little while paused. See Sprites pricing.
- Access. Rakumux serves on the Sprite’s public URL, reachable only with a Rakumux token made for
that Sprite. Your Sprites token stays on this computer, in
~/.rakumux/sprites.json. - Any machine. Sessions of any other machine running Rakumux with
remote access on can be listed here too:
rakumux machine add <name> <url> --token <its remote token>, thenrakumux new --machine <name>.