What account warmup is and why it matters
Why a new account needs warming up, which actions Lusiesta Studio imitates and how to set session length and action chances
Warmup is the period when a fresh or long-dormant account first behaves like an ordinary viewer: you scroll the feed, like something now and then, occasionally follow someone, and only after that start publishing. Below you will find why this matters, what exactly Lusiesta Studio does on the phone during a warmup and which settings the task has. For a ready-made day-by-day schedule, see 7-day warmup plan.
What a warmup is
Technically, a warmup in Lusiesta Studio is a separate task type (that is exactly what it is called in the task list, under the Activity category). The task opens the right app on the phone, goes to the short-video feed and scrolls it for a set amount of time, performing ordinary viewer actions along the way. No special platform access is involved: everything happens through taps and swipes on the real screen of a real phone, exactly the way a person would do it.
The point is to give the account a behavior history before it starts posting anything of its own. An account that uploads a video and sends out follows within an hour of signing up differs from a regular user not in its content but in its pattern of actions - and a pattern is the easiest thing to spot automatically.
How a cold account differs from a warmed-up one
A cold account is a profile with no history: an empty watch feed, no interests, zero sessions. The platform knows nothing about it beyond the device and the IP address. By the time a warmed-up account makes its first post, it has already built up:
- a watch history - which clips were watched through and which were skipped;
- reactions at varying frequency - likes on some clips rather than on every one;
- several sessions at different hours instead of one marathon;
- follows and saves spread across days instead of done in a single batch.
There is a second difference that often gets forgotten: a cold account usually has no network of its own. If ten phones go online through a single IP, no amount of warming up makes up for it - every device needs its own proxy, and the Proxies section has separate articles about that.
Which actions a warmup imitates
The warmup scenario runs in this order (the set of actions differs slightly between platforms):
- Launches the platform app on the phone.
- Closes pop-ups that get in the way, a prompt to rate the app for example.
- Opens the short-video feed: Reels in Instagram, the main feed in TikTok, Shorts in YouTube.
- Stays on a clip, captures the interface tree and rolls each action against its own chance in turn: like, save, follow, comment.
- Swipes to the next clip and repeats the cycle until the set duration runs out.
- Closes the app at the end.
In the Instagram scenario, sponsored clips are detected separately and skipped without any actions. The set of actions per platform is spelled out right in the interface: for Instagram and TikTok it is likes, saves, follows and comments, for YouTube it is likes, follows and comments.
Randomness deserves a separate mention. A tap never lands exactly in the geometric center of a button: the point is picked at random inside the central zone of the element, and the pauses between steps drift by roughly a third of the base value. Small elements are tapped dead center so the tap does not miss. Because of this, two runs of the same scenario never leave the same trace.
Warmup task settings
The Warmup settings block on the Warmup tab holds five controls, each with a slider and a numeric field:
- Duration - how many minutes the session runs. The default is 15 minutes, the range is 1 to 240.
- Like chance - the probability of a like on each clip, 25% by default.
- Save chance - 8% by default.
- Follow chance - 0% by default.
- Comment chance - 0% by default.
The chances are rolled independently on every clip, so a Like chance of 25% means roughly every fourth clip, not strictly one out of four. Duration caps the cycle by the computer clock: a pass that has already started plays out to the end, so the actual task time can run slightly longer than the value you set.
One important detail: the ranges and defaults for these controls can be sent by the server together with your license. If your numbers differ from the ones above, that is normal - go by what your app shows.
Comments and the TXT file
Comments are the only warmup action that needs data from you. The Comments block holds the Comments file row (it reads Not selected until a file is picked), the Choose TXT… button and the Delete used comments toggle.
- Prepare a plain text file: one comment per line, empty lines are ignored.
- Click Choose TXT… and point to the file.
- Raise Comment chance above zero.
If the comment chance is above zero and no file is selected, the run will not start: the app shows "Select a TXT file with comments first.". If a file is selected but has no non-empty lines in it, you will see "The TXT file has no non-empty lines.". Each comment is picked from the file at random, and with the Delete used comments toggle on the used line is deleted from the file, so it never repeats.
There are no guarantees here. A warmup removes the crude machine-like signals, but it does not override platform rules and does not protect you from a ban. The platform always makes the call, so work only with your own accounts and do not push every action chance to the maximum: more active does not mean safer.
What has to be ready before you start
- The phone is connected over USB and shows up as a live tile on the Home page.
- The input agent is installed and enabled on the phone: the Initialize agent button in the Quick actions panel on the right. Without the agent, a warmup task fails right away with a message saying the agent is not installed on the device. Details are in Siesta input agent.
- The device has its own proxy assigned, if you work with more than one account.
- You are already signed in to the right account in the app on the phone. Lusiesta Studio does not register accounts, does not store logins and does not enter them for you - a warmup works with whatever account is open on the device.
- The device fits within the phone limit of your plan, otherwise the task ends with a limit exceeded error.
How to start a warmup and where to see the result
- Open the platform section in the left menu: Instagram, TikTok or YouTube. The Warmup tab opens by default, the other tabs on these pages are marked In development.
- Select the phones in the Devices panel - there are All and None buttons and a Selected X / Y counter.
- Set the duration and the action chances.
- In the Start block leave the Now mode and click Start.
A line reading "Warmups started: N" appears under the button. A separate task is created for every selected phone, so ten devices produce ten independent tasks. From there you track them on the Tasks page: the statuses are In progress, Done, Error and Stopped, and that is also where a task can be stopped. How the task list works is covered in Creating and running tasks.
The live progress of the scenario is visible on the Logs page with a filter by device. If a task ends with an error, a diagnostic archive with a screenshot and the interface tree is attached to it automatically - the Report an error button sends it to support. A warmup does not need the video preview: even if the grid has gone to sleep and the tiles are dark, the tasks keep running.
Why you should not start with posting right away
A post is the most visible thing a new account can do: impressions, profile visits and the first audience reaction all gather around it. If the account has not had a single viewing session before that, any problem with the clip hits the whole profile rather than that one video.
On top of that, the first post usually exposes everything that is not ready: the agent has no permissions, no proxy is set, no one is signed in, the app is stuck behind an open system dialog. A warmup walks through the same screens but without the public consequences, so it is smarter to first make sure the phone runs several sessions in a row without trouble, and only then move on to uploading. After that, follow the week-long plan from the neighboring article in this section.
