Bulk actions, groups and the recycle bin

Every card in the grid and every row in the table carries a checkbox. Tick one and that profile joins a single selection, with an action bar above the list showing the count.

Select all means everything your search and filters found, not the page in front of you. The list is paginated inside the window, but the filtered set is what the actions use.

• Selection spans pages

  Paging further through the list never drops what you ticked on the pages before.

• Clearing is scoped too

  Untick select-all and you clear only what the current filter shows.

The bar carries one primary button and sixteen outline ones, and each does one thing to every selected profile. You cannot put one fingerprint on the whole batch from here: the batch would look like one machine. New fingerprint gives each profile a new machine of its own.

Move to group, Status, Rename, Tags, Assign proxy, Extensions, Password, Traffic saver and Bookmarks open a small window first, because they need a value. A confirmation stands where the action costs you something.

Fifty accounts signing in inside one minute is itself a pattern. So profiles open one at a time, with a 3 to 14 second pause before each one after the first, which spreads fifty over several minutes.

The pause applies to launch only. Moving to a group, assigning a proxy and exporting run at full speed, because no website sees any of it.

1. 1

   Check for cancel

   Press cancel between profiles: the one already opening finishes and nothing after it starts.

2. 2

   Wait out the spread

   A fresh random pause, and after it your cancel is asked for again in case you changed your mind.

3. 3

   Ask to launch

   You get back a launched profile, a real error, or the answer that there is no room.

4. 4

   Wait for room

   On that answer the profile waits five seconds and asks again, for up to thirty minutes.

5. 5

   Record and move on

   The report shows you the outcome of each profile and the first real error.

How many browsers can be open at once is decided by your machine: total memory, less 3 GB for the system, about 1 GB per browser, clamped between 4 and 32. When memory cannot be read the answer is 8, and hitting that ceiling is not a failure.

You see every bulk run as a task in the task centre, with a title, a progress bar and a cancel button. The bar moves after each profile, so a long run does not look frozen.

The ending is one of five sentences, not a green tick. A cancelled run that also had real failures says both, because cancelled on its own would hide three profiles that never opened.

Running out of room gets you its own sentence rather than an error, since nothing broke. Real errors are named alongside it.

A bulk action is one press that touches everything you selected, so every place where it could do harm silently is guarded. The delete window names the profiles, and the assign-proxy window opens with every field cleared.

An empty proxy form means remove the proxy, so it gets its own question naming the count and saying those profiles will then go online directly. The round robin tick and the library choice do not survive closing the window.

A proxy from the library stays the same record rather than a copy of it, so its checks and rotation keep working. One typed by hand you cannot save until it is filled in.

• Group already set

  If every selected profile is already in that group, you are told nothing changed.

• Partial proxy assignment

  Fewer profiles updated than you selected gets you a warning with both numbers, not a success.

• Tag in the dashboard

  A new tag joins the ones already there, because replacing would erase the labelling of a hundred profiles.

A group is a real record kept on your computer: an id, a name, a colour, a sort order and its timestamps. The same group sits in your account, so one screen shows both and neither overwrites the other when they meet.

Groups work signed out, because a group only ever describes profiles sitting in a file on this machine. A name longer than 60 characters is trimmed for you, a computer holds up to 200 groups, and a duplicate name is turned down.

You pick the colour from a fixed set, twelve in the app and seven in the dashboard, so a group never gets a shade that vanishes into the dark theme. Delete a group and its profiles come loose.

Delete is soft: the profile leaves the list with a deletion time on it, and its data is untouched. The browser is closed first, and profiles in the bin do not count against your plan.

In the bin you see two lists merged into one: what you deleted on this computer, and what your account still holds. A profile deleted on another machine appears with a badge, and you restore it from here.

The bin has a search, the choices Deleted by and Deleted, and check boxes on the rows. Restore selected brings the ticked ones back, and Delete selected permanently erases them, with the question naming how many of them the search and the choices hide.

1. 1

   Delete

   The browser is closed, the deletion time is stamped, the row leaves the list, the data stays.

2. 2

   The bin lists it

   Local and account entries are merged, newest first, with a badge on the account-only ones.

3. 3

   Restore

   You can restore a profile while you are inside your quota, and a refusal arrives in your own language. For the selected ones the room is counted for all of them before the first comes back.

4. 4

   Delete permanently

   The data goes first, then the record, and you are told whether the erase worked.

Delete permanently has to mean it, because people sell a machine on the strength of that sentence. Off the disk go the browsing data first, with retries, then the extension choices, schedules, statistics, Safe pace counters and the encrypted session file.

The browser dashboard has the same checkboxes, the same rule that Select all means everything the search found, and four actions: Move to group, Proxy, Add a tag, Delete selected.

The dashboard works through the batch one profile at a time and shows the count as it goes: there are no bulk endpoints on the server and none are needed. The first failure stops the loop, because the rest would meet the same error.

Bulk launch is not there and is not planned for there, because the browser is opened by the program on your computer. The panel says that in plain words under the bar.