v2.3.0

v2.3.0 — 2026-10-29

Client recovery for long unattended runs, the likely cause of the "wrong account on the captcha"
report, and a round of bug fixes and small conveniences. Thanks to @sjschillinger for the
client-recovery pull request (#9) and to @elia1578 for the detailed report (#10).

Changed

• "Rejoin after a disconnect" reads each client's own Roblox log instead of online status.
  Presence was the wrong signal: an account that hides its game from others never shows as in game,
  so its client was closed and relaunched every few minutes. A client is now restarted only when its
  log shows it left its game (disconnected, kicked, server shut down, a teleport or join that never
  finished). Teleports don't count, accounts with several clients are covered, online status is no
  longer needed for it, and the default wait is 1 minute.
• No more auto-minimize in the Ultra-low AFK profile. Roblox stops loading while minimized.
  Replaced by Settings → Graphics → Client windows: new clients are shrunk to the smallest size
  Roblox allows (or a size you set) and placed side by side, so they keep loading and stay connected.

Added

• Scheduled restarts. A scheduled task can now Restart: at the set time it closes the
  target's clients (or every running client when no target is picked), then relaunches them one at a
  time into the same game.
• Anti-AFK timing varies every time. The clients are visited in a random order, and each wait
  is random: before the key press (after the window has focus), how long the key is held, and the
  pause before the next client. Turn on Random timing to vary the interval between presses as well.
• Restart clients that keep growing. Optional: a client whose memory reaches a multiple (2× by
  default) of its size after its first 10 minutes is restarted into the same game.
• Anti-AFK presses the key several times per visit (3 by default, a random 1–2.5 s apart) after
  the window has had focus for a few seconds (Focus time, 2 s by default). One short tap could fall
  between the frames of a client throttled in the background, and the account was idle-kicked anyway.
• Help loading clients (Anti-AFK, on by default): a client whose log shows it still loading a game
  after 45 seconds gets focus for a moment. Roblox in the background can stall mid-load, often after a
  reconnect, until its window is focused.
• Restart one client from the Overview: closes it and relaunches it into the same game.
• "Running" filter on the Accounts page: every account with a client the manager tracks, also
  accounts that hide their game from others.
• Close Roblox in an account's right-click menu closes that account's clients (or the ticked
  accounts') and cancels their pending rejoins.
• The window opens where you last closed it.

Fixed

• A second client could be launched next to one that was still running, leaving the old one
  on "same account launched from a different device". A rejoin no longer launches when the old
  client could not be closed. A client only counts as exited once it is gone from the process
  list (one failed lookup no longer counts). A client kicked because another client of the same
  account is running, or because the account joined elsewhere, is closed and not relaunched.
• A new client can no longer hand its launch to one already running. Right before each launch
  the manager clears Roblox's single-instance lock again instead of waiting for the next timed sweep.
  A client that had recreated it took over the launch: the new process exited after 6 seconds, and
  the running client could switch accounts, which kicked the other session with "started elsewhere".
• A client that exits within a minute while a newer unclaimed client is running is followed to
  that client instead of being rejoined (the first process handed over to it); a rejoin there put two
  clients on one account.
• Healthy clients were restarted as "stuck on Starting". A client could be matched to the
  crash handler's or the installer's log, which never shows a join, so after 5 minutes it was closed
  and relaunched. Only game-client logs are matched now, a log that turns out to be another account's
  is not picked again (it was retried every 5 seconds for minutes), and a slow load gets 8 minutes.
• Stuck Roblox processes are cleared. A Roblox process with no window for 3 minutes that the
  manager didn't launch (the empty "started outside the manager" entries) is closed, and one of the
  manager's own is restarted. Such a process could keep every new client from starting until the PC
  was restarted. When a client exits within seconds of starting, the diagnostics log now lists what
  Roblox processes are running.
• Clients open windowed. With Client windows on, launches turn Roblox's Fullscreen setting off,
  and a maximized window is restored before it is shrunk. A fullscreen or borderless window is no
  longer shrunk (that left a glitchy small window).
• Anti-AFK key presses reach the game. The window came to the front but the character never
  jumped: the key was sent as a Windows key code without the keyboard's scan code, and Roblox reads
  the scan code. Each visit is now logged ("Pressed Space 3x in …'s window"), and a press Windows
  refuses is reported.
• Anti-AFK keeps retrying a window that won't take focus every minute instead of going back to the
  full interval after three tries, which could leave more than 20 minutes between key presses. When
  Windows refuses the focus, it now tries once more after a no-op key press (F13).
• A captcha could show another account's name, and solving it ended in an HTTP error kick (#10).
  The new client's launch could reach a client that was already running (see "A new client can no
  longer hand its launch to one already running" above), which then switched to the new account.
  The lock is now cleared right before every launch, and the launch waits for a sweep that is still
  running instead of going ahead after 2 seconds.
• The watchdog could put one account's name on another account's client. A client that exited
  within a minute was matched to whatever new client nobody had claimed yet, which could be another
  account's launch still starting. It now looks only once no launch is in flight.
• Starting a launch no longer freezes the window for up to 2 seconds while the single-instance
  lock is cleared.
• Schedules fire on every regional format. Where Windows writes times as 09.05 (Finnish and
  others), schedules never ran and new schedules showed "Not scheduled".
• Presets and schedules launch the right account when one account's alias is another account's
  username; the stored username wins.
• One account's own FastFlags no longer stay in effect for every account launched after it.
  They are undone by the next launch, like the Ultra-low AFK profile's flags.
• A schedule keeps its target when its account or preset disappears from the list, instead of
  silently switching to "all clients". Run now on a Restart task only restarts every client when
  no target is set, and a scheduled restart while the manager is locked no longer closes every client
  it then can't relaunch.
• Double-click and the row menu act on the row you clicked. With other accounts ticked, they used
  to launch or remove the ticked accounts instead.
• Preset names stay unique; schedules and the local API find presets by name.
• Playtime history can no longer lose a session when two clients close at the same moment.
• Removing many accounts at once saves the account file once instead of once per account (each save
  re-encrypts the whole file, which froze the window with a master password).
• "Restart clients that keep growing" reads 1,5 as one and a half, not 15.
• Hide usernames also covers the server browser's account list.
• The Overview stops refreshing its client list while another page is open.
• With more than 16 per-account proxies, the manager no longer rebuilds its connections on almost
  every request.
• Settings → Local API lists POST /preset.

---

Download: RobloxAccountManager.exe (56.5 MB) — one portable file, nothing to install.

RobloxAccountManager.exe SHA-256: 4b91c9bb8f18f770684987dcef93557cf202725cab15de2ef1b382d6e11f2335

The in-app updater verifies this checksum before it replaces anything, and keeps your previous version so you can roll back from Settings -> Updates.