Documentation

Persisted clients let the launcher keep your bots running. When you mark a client as persisted, the launcher watches it and, if it crashes or otherwise goes missing, automatically starts it again with the same identity and picks up where it left off.

How it works

While the launcher is running, it keeps track of every persisted client. If a persisted client stops reporting in for more than about 5 minutes, the launcher relaunches it. The new client reuses the original client's identity, so when it starts back up it resumes the work that was interrupted:

1. If the running script had saved resumable progress, the client continues that script from where it was.
2. Otherwise, if the client was launched with an auto-start script, it starts that script fresh.
3. If there is nothing to resume or restart, the client stops and removes itself from the persisted list.

You do not need to manage any of this manually. The script and client identity are handled for you behind the scenes; you only decide which clients should be persisted.

Launching a client as persisted

The simplest way to start is to launch a client that is persisted from the beginning.

1. Open the Tribot Launcher and go to the Clients section.
2. Click Launch Client.
3. Fill in your account, proxy, and other options as usual.
4. Check the Persist option ("auto-restart if this client goes missing").
5. Click Launch.

The client launches normally, and from that point on the launcher will keep it alive.

Marking a running client as persisted

You can also persist a client that is already running.

1. Go to the Clients section.
2. Click the client you want to persist to open its detail panel.
3. Click Persist.

Once persisted, the client shows a Persisted badge in the clients list, and the detail panel button changes to Un-persist. The client must be connected when you persist it (the launcher asks the client to register itself).

Launching many clients as persisted

If you launch clients in bulk, you can have all of them start persisted.

1. Go to the Bulk Launch section.
2. Open Settings.
3. Enable Launch as persisted.
4. Run your bulk launch as usual.

Every client started by that bulk launch will be persisted.

Managing persisted clients

The Persisted Clients section in the sidebar lists every client the launcher will keep alive. For each one you can see whether it is currently running, which auto-start script it uses, and when it was last active.

From here you can:

• Un-persist a client to stop the launcher from relaunching it.
• Schedule a resume to tell the launcher not to bring a client back until a chosen time (see below).

Stopping a persisted client

A persisted client is meant to stay alive, so there are a few things to know about stopping one.

• To stop a persisted client for good, un-persist it (in the Clients detail panel or the Persisted Clients section) or terminate it from the launcher. Both remove it from the persisted list so it will not be relaunched.
• Closing the client window directly is treated the same as a crash, so the launcher will bring it back. If you want a client to stay closed, un-persist or terminate it from the launcher rather than closing its window.

Scheduling a resume for later

Sometimes you want a client to come back later rather than right away, for example to wait out a game update or take a long break with the client fully closed.

1. Go to the Persisted Clients section.
2. Choose the client and use the Schedule resume action.
3. Pick the time the client should resume.

The launcher will leave the client closed until the scheduled time, then relaunch and resume it.

Notes and limitations

• Premium only. Persisting a client requires a premium subscription.
• The launcher must be running. Relaunches happen from the launcher, so it needs to be open. Persisted clients survive the launcher restarting (for example after an update): clients that are still alive are left alone, and any that are actually missing are brought back. After a full machine restart, your persisted clients will start again once the launcher is running.
• Jagex accounts after long downtime. A persisted client reuses its saved Jagex session when it relaunches. After a very long gap, that session may have expired, in which case the relaunched client may need you to log in again.

From the CLI

Persisted clients can also be managed from the command line:

• tribot run --persisted launches a client as persisted.
• tribot clients list-persisted lists your persisted clients.
• tribot clients unpersist <client_id> removes a client from the persisted list.

See the Tribot CLI guide for setup and details.