v1.0.326

1.0.326

• Roblox sign-in saves itself. "Log in to Roblox" opens the private browser window as before, and that is all you see: log in or sign up there, and Tempo saves the account by itself and closes the browser.
  • The small "Log in to Roblox" window that stood beside the browser, with Cancel and "I've logged in — save", is gone. So is the account screen that came up after a sign-in: a new account is named from Roblox (its display name, else its username), and Edit… changes it later.
  • The line under the account list says what is happening: which browser to sign in in, "Signed in — saving…", what was saved, or why nothing was. While the browser is open, the button reads Cancel sign-in, Re-login waits, and a second sign-in is refused instead of opening another browser.
  • It tells you whether the password was saved ("username and password saved", or "a passwordless sign-in, so only the username is saved").
• Where a sign-in is saved depends on who signed in. Roblox is asked whose session it is:
  • No more duplicate accounts. Signing in to an account you already had added it a second time. Now that account's session is refreshed.
  • A re-login never overwrites the wrong account. When you sign in as a different account than the one you chose, the session goes to that account (added, if you didn't have it), and the one you chose is left as it was. Before, the chosen account got the other account's session.
  • An account Roblox never named (added by hand) takes the ID and username of the re-login.
  • A passwordless re-login keeps a password saved earlier.
  • If the vault locks during the sign-in, it is saved at the next unlock (within 30 minutes), as before.
• The password you type is saved when you create a new account too. Only the log-in field was read, so a sign-up saved the username alone and the log said "passwordless". Any password field in Tempo's sign-in window is now read, and the value survives Roblox's jump to the home page. A passkey or "quick log in" still types no password, so only the username is saved.
• Pick a Roblox version. A new "Roblox version" row under the client line lists Automatic (what Roblox's own links open, with its version) and every RobloxPlayerBeta.exe already on your PC, in Roblox's, Bloxstrap's, Fishstrap's and Voidstrap's folders: "0.744.0 · Roblox · newest", "0.727.0 · Fishstrap". Nothing is downloaded.
  • Account launches start the picked copy. The client line checks THAT copy's signature and says "the version picked below".
  • Only a copy in one of those folders and signed by Roblox Corporation is started. Anything else is ignored, said in red, and launches go the Automatic way.
  • An older version gets an amber note: Roblox may update it, hand the launch to a newer Roblox already running, or refuse it (error 280).
  • When a Roblox update deletes the version you picked, Tempo goes back to Automatic by itself and says so.
  • The pick is this PC's, so Reset and Import keep it.
• Account fixes:
  • The local API's /relogin could open a second sign-in browser over an open one; it now answers signInOpen (409).
  • Renaming an account while it was being signed in again saved the new session nowhere.
  • Turning the account manager off, resetting the vault or closing Tempo left the sign-in browser open, its temporary profile holding a session cookie. It is closed and the profile deleted. Cleaning up after a sign-in no longer freezes the window for up to 4 seconds.
• Tempo's own scroll bars. Slim, themed scroll bars with small up and down arrows replace Windows 11's everywhere: the tab pages, the account, macro and click-point lists, the captions transcript, Live debug, the dialogs, and drop-down lists such as the 38 themes.
  • At rest a slim rounded thumb in the theme's colours; pointed at, it widens and a groove appears; held, it takes the accent. On a long list Windows' thumb is a few pixels, and the drawn one never shrinks below a short bar.
  • Scrolling is exactly what it was. Windows' own scroll bar is still there underneath and does all the work: every drag, arrow, click on the track, wheel turn, key and screen reader. Tempo's bar is a picture of it, drawn on top and transparent to the mouse.
• Live Captions:
  • Change the language while captions run. A new caption language applies straight away, without a restart, and the transcript is kept. The "restart captions" note shows only if the engine hasn't switched within 6 seconds.
  • Speaker names stay. Turning "Use faces too" on or off (or saving Settings with it changed) reset everyone to Speaker 1 and erased their names mid-conversation.
  • A long session's saved transcript starts at the beginning. The transcript keeps 500 lines, and saving wrote only those. Lines that leave it are now written to the session's file as they go.
  • The caption bar speaks your language. The engine's messages were English in every language, and "Tempo Live Captions started…" sat on the bar until the first words.
  • Fixed: a line said twice a minute apart ("Okay." … "Okay.") was dropped the second time; a selection in the transcript was lost at every caption; "N new below" carried over into a new session; the game-mode line showed a box for its emoji.
  • "Label speakers", "AI face & mouth", "Auto-start" and "Save transcripts" apply as soon as they change, on the tab and in Settings alike.
  • The Captions tab: the transcript grows with the window, speaker labels take each speaker's colour, Copy says "Copied ✓" on the button, and "All caption settings…" scrolls Settings to the Live Captions card.
• The Dim slider (Settings › Appearance › Background image) responds at once. Each step reloaded the picture and rebuilt every surface, about 45 ms a step. Now only the dimming is redone, 16–18 ms. With no picture set the slider is greyed out and says "(no image)". On a light theme Dim tones the picture towards the theme's background, and the tooltip says so. Double-click resets it to 55.
• Steadier pages. A friend's 125% laptop showed pages in pieces: controls twice at an offset, cut labels, black boxes. It didn't happen here, but the two places that hold painting back are hardened. The tab-switch picture always lifts, including after a minimise, a move, a resize or within 2 seconds at the latest, and the end of a paint freeze repaints the whole window.
• Live debug:
  • "N new below ↓" beside the filter counts lines that arrive below a reader who scrolled up. A click takes the view down to them, and it clears when you scroll down yourself.
  • A "Sign-in:" line in the Accounts section: whether a sign-in browser is open, in what, for how long, whether Tempo can see it yet, and whether a password was typed (yes or not yet, never the password or the account). Otherwise, how the last sign-in ended. A Health warning appears when the browser never answered, or has been open for 10 minutes or more.
  • Its panes have Tempo's scroll bars too. Dialogs themed by hand (the crash report, the report chooser, the tamper details, Save macro, the script step) get them as well.
  • Fixed: the stats were rebuilt under a scroll thumb being dragged and kept snapping back.

v1.0.325

1.0.325

• Anti-Freeze watches the app being clicked. It used to compare Tempo's OWN CPU use with 80%. One click thread never comes near that on a multi-core PC, so in practice Anti-Freeze was only its speed cap. Now, twice a second, it asks the window under the click whether it still answers, with the same quiet message Windows uses to decide that a program is "not responding".
  • A slow app gets slower clicks, and an app that doesn't answer gets none. While the app is slow to answer, the clicker slows down. While it doesn't answer at all, the clicks are held until it does. After 5 seconds Windows covers a frozen program with a stand-in window that drops every click, and Tempo recognises that too.
  • A full PC counts only when the app is slow too. Games often run the CPU at 100%, so a busy CPU or nearly full memory alone never slows the clicker.
  • The card shows the PC: the CPU across every core, the busiest part of the GPU and the memory in use, as Task Manager counts them, and how Windows is powering the PC ("Plugged in · Best performance", "Battery 64% · Best power efficiency"). The "CPU %" box is gone; settings files that carry its value still load.
  • Full speed while something runs. On battery and in the power-saving modes ("Energy saver" on recent Windows 11, "Battery saver" before it), Windows runs apps it thinks are in the background on slower cores and lets their timers drift. While the clicker, a macro, a recording or camera-relative movement runs, Tempo asks Windows for full speed and a 1 ms timer. It gives both back when it stops, and a paused run counts as stopped.
• Background clicks look through Tempo's own windows. With "Ignore Tempo's own window while clicking or playing a macro" on (the default), a background click aimed at a spot that one of Tempo's windows covers now goes to the app underneath, and Anti-Freeze watches that app. Before, it went to Tempo's window and was ignored there. The CPS test pad still takes Tempo's clicks. A real click on Tempo's own window is still ignored, and the status bar now says so while it happens.
• The randomizer reworked (the Randomization card and Humanize).
  • No more drift in "where the cursor is" mode. With position randomization on, each click was spread around the place the previous click left the cursor. That is a random walk: about 40 px away from the start after 1,000 clicks at ±3 px, 138 px after 20,000. Clicks now spread around the spot where you put the cursor. Moving the mouse yourself moves the spot. When the run ends, the cursor goes back to it, unless you moved it.
  • Jitter keeps the speed you set. A jitter larger than the interval was cut off at 1 ms on one side only, so 3 ± 10 ms averaged 4.01 ms and 38.6% of the gaps were exactly 1 ms. The jitter is now limited so that no gap goes below 0.5 ms (or the Anti-Freeze cap's gap). It goes equally both ways, so the average is the speed you set.
    • The rate line shows that real ± range. It showed "1–5,000 CPS" for 1 ± 5 ms.
    • Above 1,000 CPS, where Tempo picks a precise interval, the jitter was thrown away. It applies there now too.
  • A round spread that stays in its window. X and Y were randomized separately, which made a square that reached 1.4 times the set radius in its corners. Clicks now fall in a circle, most of them near the middle. A spread near a window's edge could click the app next door. Each spot is now checked to be on the same window and on screen; when it isn't, the click lands on the spot itself.
  • Burst pauses vary with the clicks. A pause between bursts moved by ± the jitter in milliseconds, so a 1-second pause varied by only ±10 ms. It now varies by the same share as the clicks, up to half. A press length varies by at most half of itself.
  • Changes apply to a run in progress: randomize on or off, jitter, spread and press length, as the interval already did. Loading another profile applies its values as well.
  • Each run has its own randomness. All runs shared one random generator, which is not safe when a stopping run and the next one overlap.
  • Humanize fits the speed. It added at least ±5 ms, even at 1–4 ms. It now adds:
    • about 20% of the interval, never the whole interval;
    • ±2 px of spread, except in key mode;
    • a natural press length when none is set: 30% of the interval, at most 80 ms, and none under 3 ms.
    • Turning Humanize off puts the press length back only if you haven't changed it since.
  • Greyed out where it can't apply. Position randomization does nothing in key mode. "Restore cursor position when stopped" applies only when the clicker moves the real cursor.
  • Fixed: "Restore cursor position" moved the mouse after a keyboard run. A key run never moves the cursor, but its end still "restored" it, and the mouse jumped back to where it was at the start.
  • Three tooltips explain what the jitter and Humanize do, in all six languages. German now says "Salve" for a burst everywhere. The card said "Burst" while the Mode menu said "Salve".
• Fixed: Hold mode stopped and started constantly when the trigger was the key being pressed ("hold E to press E"). Windows reports a key Tempo presses the same way as one you press. So every key-up Tempo sent looked like you letting go, and the clicker stopped and restarted at the key's repeat rate, starting a new run each time. In that setup Tempo now watches the key on your keyboard itself.
• Roblox update alerts.
  • What Tempo asks. Every 2 hours while Roblox is installed, Tempo asks Roblox which client it has released. It uses the same public address Roblox's own client asks, and nothing about you or your accounts goes with it. It also reads Roblox's public deploy log for a newer build that has been uploaded but not released yet.
  • The choices. When the released client is newer than the one on this PC, a card offers Update now, Later (24 hours) or Keep this version. Roblox updates itself through its tray process and turns away old clients after a while (error 280), so Tempo can't keep an old version for you. "Keep this version" means no reminders until a release newer than that one.
  • Update now runs Roblox's own updater, after checking that Roblox signed it. For the Microsoft Store version, it opens the Store's updates page. It asks first if a Roblox window is open.
  • Launchers such as Bloxstrap get one notice, and Tempo never runs Roblox's installer over them, which would take the Roblox links back from the launcher.
  • Where it shows. The notice clears by itself once Roblox has updated. The Accounts row's "Update Roblox…" button, the Roblox client window's "Updates" section and Live debug show the state. Settings › Behaviour › "Check for Roblox updates" turns it off, and the privacy panel lists it.
• Sign in with any Chromium browser. The sign-in browser picker knew four browsers by name and path: Chrome, Edge, Brave and Opera.
  • Every installed browser is found: the ones Windows lists as browsers, the ones registered as apps, and the usual install folders. That covers Opera GX and Air, Vivaldi, Yandex, Chromium, Thorium, and the Beta, Dev and Canary channels of Chrome and Edge.
  • Judged by its files, not its name, so any Chromium browser can sign in.
  • Firefox-based browsers (Firefox, LibreWolf, Waterfox, Floorp, Zen) are listed as "can't be used for sign-in", and picking one says why.
  • Windows' default browser is marked, and a saved choice of Chrome, Edge, Brave or Opera stays as it was.
  • Live debug lists the browsers found, and warns when the chosen one has been uninstalled.
• Fixed: Roblox wouldn't launch after it updated itself. Roblox deletes the old version's folder when it updates, but on one PC its roblox-player: links still named the deleted program. Tempo saw that, said "Roblox is only partly installed" and refused every launch, while Roblox was running. It also put "Get Roblox" where the game preview goes. Tempo now starts the installed client directly in that case, with the link it was given. It doesn't rewrite Roblox's registry entries, so the website's Play button stays broken until Roblox registers its links again.
• The Accounts window opens where you can see it. With Accounts in its own window, three things hid it:
  • With "Always on top" or full screen, the main window floated and the Accounts window opened under it. It now floats with the main window.
  • Its first size was taller than a laptop's screen (1025×900 at 125%), and a size saved on a big monitor came back just as big. It now always fits on a screen.
  • From the tray, Windows refused to bring it in front of the app you were using. It now comes to the front.
  • If opening it fails half-way, the accounts stay on the tab.
• Fixed for laptops at 125% and 150%. On a 1920×1080 laptop at 150%, several screens Tempo draws itself kept 100% sizes while their text grew to 150%. Every one of those sizes now scales with the screen; at 100%, nothing moved by a pixel.
  • The saved macros list wrote names over cut-off details.
  • The splash screen's tagline touched both edges of its card.
  • The statistics charts, stat cards and notification cards ran their text into each other.
  • The window fits the screen on first start. Unless "Remember window position" was on, nothing fitted a 150% window to the screen. It came up bigger than a laptop's screen, with its title bar above the top edge.
  • Two texts were cut off at 150% in every language: the Live Captions model note and the bug-report chooser's log hint. Both have room now. Tempo's own layout check missed them, because it let a wrapped text lose its last line.
• Spacing: the "UI noclip" fixes.
  • Spinners looked like "[ 100 ]". Every number box drew a second, square frame around its digits, inside its own outline. That frame is go...

v1.0.324

Tempo v1.0.324

A major update focused on reliability, accessibility, performance, and usability across Tempo.

✨ Highlights

• CPS Test improvements — Detailed click-speed statistics, separate records by input and test duration, and more accurate timing.
• Improved game movement — Better camera-relative movement, precise turning calibration, fine steering, and keyboard-layout support.
• Windows Live Captions diagnostics — Check whether Windows Live Captions works with Tempo, identify problems, and access troubleshooting options.
• Smarter notification mirroring — Display website names, icons, pictures, progress bars, action buttons, and full notification messages.
• More reliable updates — Improved GitHub rate-limit handling, proxy support, and automatic retry scheduling.
• Account vault reliability — Prevent account changes from being lost when the vault locks and report save failures clearly.
• Improved macros and keybinds — More reliable mouse-button bindings, safer recording, and better playback monitoring.
• Performance improvements — Reduced unnecessary disk writes, corrected RAM reporting, and moved slow diagnostics into the background.

🐛 Bug Fixes

CPS Test

• Fixed clicks being counted after the timer expired.
• Fixed the final click accidentally starting a new test.
• Fixed duplicate counting when starting a spacebar test.
• Added separate personal records for each input and test duration.

Game Movement

• Fixed camera-relative movement counting mouse movement when the camera wasn't turning.
• Improved full-turn calibration accuracy.
• Fixed movement settings restarting against the wrong window.
• Fixed hotkeys becoming unresponsive when Tempo's window was busy.
• Fixed movement not following a game after it restarted or rejoined.
• Improved movement accuracy between the eight standard directions.

Live Captions

• Added a Windows Live Captions diagnostic report with checks, timings, and troubleshooting actions.
• Fixed transcripts being cleared when changing caption settings or switching engines.
• Fixed caption windows becoming difficult to move or snapping back to their original positions.
• Improved font previews, appearance settings, and multilingual text.
• Fixed transcript files overwriting earlier saves.

Notifications

• Improved notification cards to match Windows' displayed content.
• Fixed repeated notifications being silently dropped.
• Fixed Windows notifications being cleared before Tempo displayed their cards.
• Added website-specific muting, functional notification buttons, and improved notification history.
• Improved support for reminders, alarms, progress bars, and long messages.

GitHub and Updates

• Improved handling of GitHub API rate limits.
• Added support for configured Windows proxies during update checks and downloads.
• Improved retry scheduling and rate-limit reset timing.
• Fixed update checks incorrectly reporting certain access-denied responses as rate limits.

Account Vault and Local API

• Fixed account changes being lost when the vault locked during an operation.
• Added clearer errors for failed saves and unsuccessful removals.
• Kept the local API available while the vault is locked, with account operations blocked until unlock.
• Added API lock-state reporting and a notification-based unlock request.

Interface, Hotkeys, and Macros

• Fixed incomplete window rendering during startup and reopening.
• Improved overlay positioning, opacity, and click-through behavior.
• Fixed mouse side-button hotkeys and macro-recording conflicts.
• Improved Windows shortcut handling during clicker and macro runs.
• Improved the Macro Live Monitor to display every step, including large macros.

⚡ Performance

• Reduced repeated disk operations when writing logs.
• Improved log rotation and retention.
• Corrected the RAM figure to match Task Manager's private working set.
• Moved Windows diagnostics off Tempo's main window thread.
• Improved rendering and macro-list performance.

🔒 Privacy and Safety

• Logging stops immediately when disabled, with an option to delete existing logs.
• Diagnostic reports no longer list every window title.
• Notification pictures are not saved to disk.
• Notification images are read only from local Windows data; Tempo does not fetch images from the internet.
• The local API remains loopback-only and token-gated, and it never accepts the vault's master password.
• Dangerous notification links that could execute files or scripts are not opened.

🌐 Localization

• Fixed untranslated interface text.
• Improved keyboard-layout support.
• Improved caption text, font selection, and button labels across supported languages.

---

Full changelog: See the changes listed above for details.

Version: 1.0.324

v1.0.323

Tempo v1.0.323 — Summary

Tempo's main goal in this update is to make the app faster, improve live captions, fix bugs, and make the interface easier to use.

Biggest improvements

Live captions are smarter: Better speaker identification, speaker names, and matching faces to voices.

Fewer false captions: Silero VAD filters out music, fan noise, gunfire, and other sounds without speech, reducing invented words.

Better caption text: Fewer repeated words, better punctuation, and more accurate speaker labels.

Faster startup: Tempo starts about 3 times faster, with idle CPU usage reduced significantly.

Smoother interface: Switching tabs is faster, screens no longer flash during transitions, and fewer operations freeze the app.

Better laptop support: Fixes for Windows display scaling at 125% and 150%, smaller screens, and cut-off text.

Improved accessibility: Better text contrast, clearer colors, readable tooltips, and improved translations across six languages.

Hotkeys work better: Shortcuts can work while holding Shift or Ctrl, and conflicting shortcuts receive clearer warnings.

More reliable macros and profiles: Fixes for recording, playback, importing, renaming, switching profiles, and saving changes.

Better caption controls: Caption windows can be moved, resized, positioned, and kept visible over fullscreen games.

Roblox account manager improvements: Better account security checks, encrypted account storage, clearer warnings, and more reliable launching and following players.

Improved Local API: More reliable account launching, private-server support, clearer errors, and better debugging information.

More reliable updates: Downloads can resume after connection problems, checksums verify completed files, and failed installations give clearer messages.

Better notifications and debugging: Fixed duplicate events, slow logs, missing notifications, and problems with scrolling and copying logs.

Improved HDR and themes: More accurate colors with HDR enabled, consistent menus, and better readability across 38 themes.

Windows startup fixes: Faster background startup and more reliable automatic launching.

Better security and stability: Improved Roblox client integrity checks, safer macro imports, and fixes for freezes and memory leaks.

Overall

Tempo v1.0.323 is a major reliability and performance update. The biggest changes are smarter live captions, faster startup, lower idle CPU usage, better speaker recognition, smoother UI, and more reliable hotkeys and macros. It also improves Roblox account management, security checks, and updating.

v1.0.322

1.0.322

Private servers actually join your private server · picking another account no longer lands you in your main one · live captions stop freezing mid-sentence · the account screens redesigned · a lot of things that were quietly wrong

• Fixed: a private server ID did nothing — and did it silently. Whatever you typed in the private server box was sent to Roblox as an accessCode. The code everybody actually has is the one out of a private server link, and that is a different parameter (linkCode) — sent in the wrong field it does not fail loudly, the client just joins the public game instead. So the launch looked like it worked, and you were never in your server. Tempo now reads whatever you paste: the old-style roblox.com/games/…?privateServerLinkCode=… link, the newer roblox.com/share?code=…&type=Server one (including the shortened form the app hands you), a bare code, or the owner-only access GUID — and sends each to the right parameter. Paste the link into the Place ID box instead and Tempo moves the code to where it belongs rather than throwing half of it away, which was a second way to end up in the public game. A short note beside the box says which kind Tempo thinks it has, and if a code can't be used, nothing launches — rather than five accounts quietly joining the wrong server.
• Fixed: choosing another account could launch you as your main account. Roblox allows one client at a time, so while a client is open Windows hands a new launch link to that client — which stays signed in as whatever account it already has. The session ticket Tempo minted for the account you picked was simply ignored, the join happened as the other account, and Tempo still reported "Launched" with nothing anywhere recording which account actually went in. Now, when a client is already running (and multi-instance is off), Tempo asks first: close it and launch as the account you chose, launch anyway, or cancel. Multi-instance is never switched on for you — that carries a ban risk and stays your decision.
• Live captions no longer freeze for tens of seconds. One awkward chunk of audio could send the speech model into a retry loop that took 10 to 73 seconds to finish, and captions simply stopped during it. The decode is now bounded (no temperature fallback, a token cap, a narrower beam), so a bad chunk costs a moment instead of a minute. The delay figure the caption bar reports was also double-counting — it read 4.3 s when the true lag was 2.0 s — and the saved transcript stored each line three to six times over when speaker labels were on. Joining two captions across a chunk boundary no longer stutters the word it landed on.
• The Accounts screens were rebuilt. The unlock and "set a master password" screens were a title, a field and some buttons scattered across four different left edges against a wall of black, with a hole in the middle where an error message would one day appear. Each is now one card, centred, with the field full width, a single obvious button, and that middle line carrying something useful when nothing is wrong ("Press Enter to unlock", or the password rule) instead of sitting empty. On the account list, the Roblox client line ran underneath the column of buttons on the right, the private server box was a stunted half-width next to the Place ID box above it, two different buttons were both painted as the primary action, and three labels were cut off in languages other than English. All fixed, and all six languages are now measured automatically so it cannot drift back.
• Tempo can now tell you exactly which Roblox client it checked. The Accounts tab has a Details… view: which program answers Roblox links, the client version a launch will really run (0.739.0.7390687, not just a folder name), who signed it, when that certificate expires, and every copy on disk — there are usually three, they are ~130 MB each, and the one that runs is not always the newest. It is plain text, and the Copy button puts exactly what you see on the clipboard.
• Fixed: a wrong clock could accuse Roblox of being tampered with. Every failing signature check was reported the same way — "your Roblox client looks modified — launching may be unsafe", in red. An expired signing certificate (usually your PC's clock), a certificate chain Windows cannot build, and a check that could not run at all were all shown as tampering. Those now say what they actually are, and a check that did not run says nothing either way rather than accusing anything.
• Notifications you couldn't see are now handled properly. Cards waiting behind the five on screen ignored the fullscreen rule that the visible ones obey, so a card raised before a game started could paint over it minutes later; that queue also had no limit and nothing ever went stale, so a burst from one chatty app could still be arriving long after the thing it was about. Waiting cards are now dropped when they can no longer be shown or are simply too old — into the history, with the reason, at the time they were raised — and repeats of the same message fold into one card with a count instead of a column of twins.
• Mute one noisy app instead of turning off mirroring. Right-click a mirrored notification to mute that app; Settings → Notifications → Muted apps lists what is muted, and can mute an app Tempo has already seen. A muted notification is still written to the history with the reason, so nothing vanishes without a trace. Right-clicking a card no longer launches the app that sent it, which was the only gesture on a card that did something you hadn't asked for.
• The local API answers the address your script actually uses. It bound only 127.0.0.1, but on Windows "localhost" resolves to ::1 first — so half the HTTP clients out there got "connection refused", which reads exactly like Tempo not running. It now binds both. /relogin opens a real sign-in window and had no rate limit (a loop opened twenty in a second); it does now. And the server counts what it has been asked to do — requests, refusals, and the last call — shown in Live debug and in the API dialog, because "my script does nothing" previously left no trace anywhere.
• Live debug tells you more, and reads better. It reports the Roblox client version and warns when its signing certificate is close to expiring, what the local API has served, what the notification queue has dropped, which apps are muted, and how long Tempo's own low-level keyboard/mouse callbacks take — Windows silently removes a hook whose callback overruns, which until now would have stopped hotkeys with nothing in the log to say why. Its own control strip also wraps instead of overlapping in five languages, and account-manager lines are coloured like every other subsystem.
• Fixed: the vault's own error messages were English-only. "That master password is not right", "this vault belongs to a different Windows account", and eight more — the messages you meet precisely when something has gone wrong — were the one part of the Accounts feature that never got translated. They speak all six languages now.

v1.0.321

1.0.321

A Roblox account manager, with an encrypted vault and no typed passwords · every notification is kept, including the ones Windows threw away · Tempo survives a Windows restart properly · "Start with Windows" stops silently breaking

• New: an Accounts tab — a Roblox account manager built into Tempo. Keep several Roblox accounts, launch any of them into a game by Place ID, follow a player into whatever they are playing, and switch between accounts without signing in and out. It is a ninth tab, it is off until you turn it on, and the switch says plainly what it does before you do. Everything below is part of it.
• You never type a Roblox password into Tempo. Signing in opens your own browser — Chrome by preference, then Edge, Brave or Opera — in a private window, and you sign in to Roblox exactly as you always do. Tempo takes the session from that window when you are done; the password is never typed into a Tempo field and never travels through one. If you sign in without a password at all — a passkey, or Roblox's "quick log in" — Tempo notices and saves only the username, because there is no password to save. That distinction shows in the account's menu, so "no password saved" reads as passwordless rather than as something that failed.
• The vault is encrypted twice, and locked by a master password you choose. Sessions and any saved passwords are sealed with AES-256-GCM under a key stretched from your master password (PBKDF2-SHA256, 1.2 million iterations), and that file is then sealed again by Windows to your account with DPAPI. The consequence worth understanding: a wrong master password does not "fail to log in", it fails to decrypt — there is nothing to guess against and no copy of the password anywhere, so if you lose it the vault is gone and the only way forward is to start a new one. Optionally the vault re-locks itself the moment you switch to another tab.
• A coloured dot per account says whether its session still works — and Re-login is offered the moment one doesn't. Tempo checks each saved session against Roblox and marks it green (good), red (expired), or amber (not checked yet), re-checking in the background while the list is open. When a launch fails because a session had quietly expired, Tempo now says so and offers to sign that account back in on the spot, instead of leaving a warning that told you to go and find the Re-login button yourself. Re-login is also available whenever a selected account's dot is red, not only when exactly one row is selected.
• Type a Place ID and the game identifies itself. The name, the creator, its icon, and how many people are playing it right now, with likes, total visits and the server size — so a mistyped ID is obvious before you launch eight accounts into it. Reading it needs no account and no cookie.
• Running more than one Roblox client at once, without administrator. Roblox allows one client per PC by holding a single lock; Tempo closes that lock so further clients can start. It does it by asking Windows to close the handle, from a normal user account — Tempo does not modify Roblox, inject into it, or need to be run as administrator, and a dot reports whether it is genuinely working, idle, or being blocked. Stated plainly: running several clients is against Roblox's rules and can get accounts banned. Tempo asks, every time, before turning it on, and says exactly that in the question.
• Everything on the page speaks your language. The whole tab — every label, warning, menu and error, about 160 phrases — is translated into all six languages Tempo supports, rather than being an English island inside a translated app.
• Every notification Tempo raises is now kept, especially the ones you never saw. Notifications shown while a fullscreen game had the screen were dropped, and only a count of them ever reached the log — so the one case where you certainly missed the message was the one case with nothing to read afterwards. There is now a history you can open, with what was shown, what was suppressed and why.
• Tempo no longer holds up a Windows shutdown, and stops losing your settings to one. Two faults, both only visible at a restart. With a clicker or macro running, Tempo answered Windows' shutdown with a modal "exit anyway?" question — which nobody is present to answer at 3am when Windows Update reboots, so it stalled the shutdown, put Tempo on the "this app is preventing you from shutting down" screen, and ended with the process being killed anyway, losing the settings the question had delayed. And there was no handling of the session ending at all: Tempo's ordinary shutdown work (stopping the engine, saving a caption transcript, restoring devices) is far longer than the few seconds Windows allows, so a reboot could take the process down before a single setting reached disk. A shutdown, restart or sign-out is now never asked a question, and the state that has to survive a reboot — window position, the tab you were on, Settings changes, clicks counted so far — is written the instant Windows says it is ending the session.
• Fixed: "Start with Windows" could silently stop working, while still looking switched on. The sign-in entry was rewritten to point at whichever copy of Tempo you last ran. Open a portable copy, a build of your own, or an update staged in your Downloads folder just once, and your sign-in entry quietly moved to that file — then that file gets deleted or the stick comes out, and Tempo stops starting with Windows. Nothing said so: the checkbox still read ON, because the entry was still there, just pointing at nothing. The registered copy is now left alone while it still exists, and is only repointed when it has actually gone.
• Live debug learned about the two things it could not see. It now reports whether Windows will actually launch Tempo at sign-in — including the two overrides that leave the checkbox looking fine, a Task Manager "Startup apps" disable and an entry whose program file no longer exists — and it reports the Accounts tab: vault state, how many sessions are good, expired or unchecked, and what the multi-instance lock closer is really doing as opposed to what the switch says. Both also raise a line in the Health summary at the top.
• Windows itself is named in the diagnostics, with a note when the version is older than Tempo supports, and the display panel now reports colour depth and HDR — which is what explains a theme looking washed out on an HDR monitor.
• Fixed: the version shown in Settings → Apps went stale. Tempo's entry in Windows' installed-apps list kept whatever version first registered it, so an updated copy still advertised an old number to Windows. It is refreshed on launch.

v1.0.320

1.0.320

A build ID, so a test copy can never be mistaken for this release · search the Settings page · your own logo everywhere, not just the header · three things that were quietly wrong

• Every build now carries an ID, and says so when it isn't an official release. The version number could never answer "which copy is this?" — a test build carries the same number as the release it was cut from, so the two looked identical everywhere the version was printed. Each build is now stamped with the time it was made, to the minute, in UTC: build 260902-2123. Anything that is not an official release also carries a TEST badge, in the warning colour, at the bottom of every screen — plus the About box, the Settings page, the splash, the first line of the log and the diagnostics attached to a bug report. This release says build … with no badge; if yours shows TEST, it did not come from the Releases page.
• The Settings page has a search box. Roughly sixty settings had accumulated across eight cards and about two thousand pixels of scrolling, with nothing to find one by. Type and the matches light up, with a count of how many and in how many sections; Enter jumps to the first, Escape clears. It searches the explanatory tooltips as well as the visible labels, so words that appear nowhere on screen still find the right switch — typing "CPU" finds the anti-freeze limit, whose label never mentions the CPU.
• The Settings cards now lay themselves out. Every card's position on that page was a hand-written number, and twice in the past a card that grew was left overlapping the one below it — hiding its title and the top of its first row. Nothing failed and nothing was logged; it simply looked broken. The page now works the positions out from the cards themselves, so that cannot happen again, and the Save row and the notes below always follow the last card down.
• A custom logo now shows everywhere, not just in the header. Choosing your own image in About changed the header wordmark and nothing else: the window icon, the taskbar button, the tray icon, every dialog's title bar and the pop-up notifications all kept Tempo's built-in mark until the app was restarted, and some of them never changed at all. They all follow the logo now, and update the moment you pick it. The image is also rebuilt at each size Windows asks for — 16px through 256px — instead of one large copy being squashed down, which is what made a custom logo look soft in the title bar next to everything else.
• Fixed: "Unsaved changes" was showing permanently. The Clicker tab compared your current settings against the profile you loaded to decide whether anything had been edited — but one of the values it compared was the moment the comparison ran, so the two could never match. The warning appeared a moment after loading any profile and never went away, including immediately after saving. It now compares only the settings the Clicker tab can actually change.
• Fixed: the sidebar icons wore each other's colours, and Settings had none. Each tab's icon is tinted its own colour. When the Profiles tab was added, the list of icons was updated and the matching list of colours — kept in a different part of the file — was not, so every icon from Profiles downwards took the colour belonging to the tab below it, and Settings, falling off the end of the list, was left grey. Both lists now sit together with a check that complains if one is ever short again.
• Fixed: the log claimed the wrong version. The first line of every log file had the version number typed into it by hand, so it would have gone on reporting 1.0.319 out of every release after it — in the line most likely to be quoted in a bug report. It reads the real version now.

v1.0.319

1.0.319

Tempo checks it hasn't been tampered with · bug reports stop leaking your account name · Live Debug's colours finally mean something · ~150 strings that were never translated

• Tempo now verifies its own program file, against GitHub. On every launch it hashes Tempo.exe and asks GitHub what the release for that version number is supposed to be — using the SHA-256 GitHub publishes for the release asset itself, so nothing is downloaded and no extra file has to ship. Three answers: verified against the release on GitHub, does not match the release published for its version number, or no release with this version number exists. That last pair is the point — a patched build handed out under a real version number no longer passes, and neither does one carrying a version that was never published. Tested against a genuine download of v1.0.316: it comes back verified against its own release and modified against any other. Also catches a damaged file — a byte-patched copy, a half-zeroed one, a broken executable header, or a bundle with the speech libraries stripped out. Settings → Data & Backup has the switch, Check now, and Trust this copy for a build you made yourself. Honest limit: this is tamper-evident, not tamper-proof — it will not stop someone who edits the check out too, and being offline is never treated as evidence of anything.
• Bug reports no longer carry your Windows account name. Eight of the nine report bodies Tempo can produce sent it verbatim, along with your full user folder path — the redaction existed but was wired to one code path, the crash report, and nothing else. Even a crash issue put the raw exception message in its title while the body beside it was clean, so the one part you could not review was the one part that was not cleaned. Account name, PC name and personal folders are now stripped from every report and every subject line, matched on whole words so a short account name cannot chew through unrelated text.
• "Report a bug…" shows you the report before it sends it. Both reporting buttons now open the same composer: the complete text, editable, with the privacy position stated where the decision is made — and nothing leaves until you pick a way to send it. The recent activity log is offered rather than attached silently; it can mention files you have opened, so it is a tick-box you can read first. If the report is too long for your email app to carry — which it is once the log is attached — Tempo offers the clipboard instead of letting the mail client cut it off mid-sentence.
• Live Debug's colour coding was largely fiction. The legend advertised a "clicker" colour that nothing in the app could ever produce, because no line was tagged as coming from the clicker. Half the subsystems had no colour at all — scripts, the second cursor and second mouse, macros, the caption overlay, the word fixer, window and tray events. And the classifier matched words anywhere in a line, so it read quoted interface text: every one of the 30 lines that matched its clicker test was a German layout warning quoting the caption setting "GPU-Engine ausprobieren". It now reads the subsystem tag from where the tag actually is. Every category fires, nothing falls through uncoloured, and script steps get their own colour.
• Around 150 strings that had never been translated, in any language. The audit could not see three whole shapes of string: a caption chosen with a ternary (on ? "Stop captions" : "Start captions"), text passed through a helper that translates it later, and a window title assigned without this.. So five of the six buttons in the bug-report dialog, about twenty window titles including the crash dialog, and the second half of every two-state button had shipped in English — a Spanish user pressed "Iniciar subtítulos" and watched it become "Stop captions". The speaker labels on the caption bar are translated now too, and the words on the keyboard shortcut keys follow the legends printed on a keyboard in that language rather than a dictionary.
• Settings survive a crash. A hard freeze on 2026-08-31 left settings.json at its exact full length with every byte zero — the file was atomically replaced, and Windows lost the contents anyway. There was no second copy. Tempo now keeps the previous save beside it and falls back to it when the current one will not load, so an interrupted write costs one save instead of everything. An unreadable settings file also used to reset every preference with no log line and no preserved copy, looking exactly like a first run.
• Fixed: the CPS test opened with four English labels among translated ones, which then switched language on the first click.

v1.0.318

1.0.318

A run can no longer click Tempo's own interface · the window comes back the way you left it · the running badge stops cutting itself off · second-mouse fixes

• A running clicker or macro can no longer operate Tempo itself. Injected input goes to whatever window sits under the pointer, and Tempo is just another window — leave the cursor over it and a run ticks checkboxes, drags the speed slider and switches tabs at full speed. A macro is worse: it replays coordinates recorded somewhere else entirely. Every event Tempo injects now carries a signature the app recognises and ignores on its own windows. Real clicks and keys never carry it, so Stop, Escape and the tray always work — which is the point, because that is exactly when you need them. Measured: 1,018 self-clicks fired at the window across three runs, 2,036 messages ignored (a down and an up each), target speed unchanged; with the switch off the identical run drove it 67 → 200 CPS. New option in Settings → Behaviour, on by default, and it applies the moment you tick it rather than waiting for Save.
• Minimising and restoring behave. Sending a maximised Tempo to the tray and reopening it handed back a normal-sized window; it now returns maximised. The Show/hide-window hotkey kept a private copy of the tray logic that had drifted into a worse version of it: the window blinked out instead of playing the minimise animation, came back forced to normal size, and — pressed while Tempo was merely minimised — hid it further instead of showing it, taking two presses to undo. "Hide to tray when clicking starts" animates now too, rather than vanishing the instant you press Start.
• The on-screen running badge sizes itself to what it shows. It was a fixed 232 px wide with its text drawn at a fixed offset and never measured, so a long line ran off the end — 1,234,567 clicks · 199.9 CPS · 1:23:45 needs 214 px of the 198 available, which is exactly the long, fast run where you are watching the badge instead of the window. It grows to fit now, and shrinks back. The optional hint line also pushed a bottom-anchored badge further down toward the taskbar it was meant to clear; it re-places itself now.
• The "running overlay" dialog wears the theme. Windows' own blue checkboxes, a Win32 drop-down and square buttons sat among Tempo's controls; all replaced, along with a font that was built per dialog and never released.
• Second mouse. Relaying a physical press from the second mouse onto Tempo's own window works again — it carries a different signature from automation, so reaching over to hit Stop mid-run is no longer ignored. Spam-clicking refuses to target Tempo's own windows (it posts messages rather than injecting, so the protection above cannot see it). And a pointing device that reports absolute screen positions — a drawing tablet, a touchscreen, a remote-desktop pointer — now says so, instead of counting as your second mouse and then silently never binding however much you wiggle it.
• Fixed: scrolling the Settings page with the pointer over the Window-opacity slider changed the opacity instead of scrolling the page. It was a stock Windows slider, which also made it the one grey control on a themed page.
• Fixed: finishing a macro recording popped the window back up and stole focus even when you had minimised Tempo yourself — the rule playback already followed.
• Live captions start more reliably, read system audio better, and report GPU/CPU use honestly; the model download resumes instead of starting over. Caption history appears without the delay that made it look empty.
• Notifications are off by default on a fresh install, animate smoothly instead of in frame-counted jerks, and hold themselves back during full-screen games and Do-Not-Disturb. Fixed a crash after using the tray's pop-up-notifications item.
• Dragging the window is no longer heavy, the tray menu animates, and switching tabs paints the whole page the first time instead of leaving parts of it blank.

v1.0.317

1.0.317

Your background image now covers the whole window · the window comes back intact after minimising · title-bar buttons keep focus

• The background image finally reaches the page. The wallpaper showed on the header, sidebar and footer band, but the main content area stayed a flat grey slab. The page had full backdrop support all along — it was never switched on, because the backdrop is applied while the window is still being built (the tab control has no handle yet and reports no selected tab), and the code that would switch it on later never fires when the remembered tab is the first one. Switching tabs once used to fix it for the session. Verified on a cold start and all six tabs: page RGB(84,35,44) against sidebar RGB(83,35,43) — one continuous image across every surface.
• Fixed: the window came back damaged after minimising. Restoring could strip the header of its logo, profile caption and ─ □ ✕, or leave a black void over the lower two-thirds with the desktop showing through the sidebar. The restore repair only repainted the tab pages, so every other surface kept whatever was in the buffer when the window went down. Measured after the fix: 0.0% unpainted pixels across five minimise/restore cycles, and clean through a maximised round trip.
• Fixed: minimise/maximise/restore could leave Tempo behind another window. Windows refuses to bring an app forward when something else owns the foreground; the caption buttons now take it properly.
• The maximise/restore glyph stays correct through every route into and out of maximised.