SessionDock 3.1.2

SessionDock 3.1.2

Release approval

• The v3.1.1 workflow passed build, signing, and Defender but created no draft because Velopack omitted the verified Microsoft createdump.exe runtime file from the NUPKG. Version 3.1.2 disables that built-in omission after the strict publish allowlist, preserving exact app-file equality with the portable ZIP.
• The zero-asset distribution hold dated 2026-08-04 is lifted only after this exact version passes the protected draft, separate-laptop Defender and standard-user smoke test, independent publication approval, publication, and anonymous public re-download gates.
• SessionDock remains an unsigned personal project. The supported manual download is the complete transparent Windows x64 portable ZIP from the official GitHub release, never a loose executable or Discord attachment. Any named antivirus detection stops use and distribution.

Sessions from one home screen

• Home keeps Launch accounts, Run template, Macros, and Templates prominent, with direct Destinations and Manage accounts tiles below. The advanced workspace remains available in Settings.
• Reusable destinations require names, support account assignments, and stay synchronized across Home, advanced settings, batch launch, and template editing. Per-account custom destinations remain compatible.
• Templates save selected accounts, destinations, scalable window positions, launch timing, and ExactWheel assignments. Export and import can carry selected macros, public-safe destinations, templates, and batch presets while excluding sign-ins, cookies, tokens, tickets, private-server data, integrations, logs, and local account paths. Macro files can contain typed secrets, so keyboard-bearing macros require explicit acknowledgement.

Scalable layouts and continuous macros

• Batch launch can arrange Roblox windows as a configurable staircase with human-sized focus areas. Saved layouts use stable monitor identity and relative coordinates so compatible 4K and 1080p screens can adapt safely.
• ExactWheel recording and playback are built into SessionDock. Record the focused client or whole layout, choose a customizable global recording-stop key, manage the macro library, and assign one client macro to several selected clients.
• Playback loops until the user explicitly presses Stop, closes the controller, starts a replacement batch, or exits. Focus loss, a temporarily unavailable target, physical-input protection, and slow clients pause without injection and retry when safe instead of silently ending.
• Small bounded focus-settle delays keep inputs from colliding between clients. Verified process and window leases, bounded caches, shared display snapshots, allocation-free timing paths, throttled controller progress, and suspended idle browser work reduce CPU and memory overhead for sustained n-client use.
• Roblox windows are arranged without forcing unrelated applications permanently behind them. Exact process, PID and HWND ownership, foreground, pointer, physical-input, and injected-input cleanup checks remain active at dispatch boundaries.

Guidance, integration, and packaging

• First launch includes a Get Started tour for accounts, named destinations, launching, layouts, recording, and templates, plus a separate Advanced tour. Tutorial cards avoid highlighted controls in small windows, and clipped or off-screen targets no longer freeze or crash the tour.
• HandleScope ships as an inspectable SessionDock component and needs no separate installer, PowerShell script, or execution-policy change. Reviewed compatibility options for the independently available HandleScope project remain supported.
• The release has no Setup program, single-file bundle, self-extractor, or Authenticode signature on SessionDock-owned executables. The protected workflow verifies exact application bytes, Microsoft runtime signatures, update metadata, the version-bound HandleScope catalog, checksums, SBOM, component provenance, Defender results, GitHub attestations, and anonymous public asset equality before announcement.

SessionDock 2.9.0

SessionDock 2.9.0

Policy-independent HandleScope setup

• SessionDock now includes a closed native HandleScope setup adapter. A signed catalog release that declares the reviewed native capability can run only the fixed api/HandleScope.Setup.exe executable with the compiled verify and install phases; catalog data still cannot provide a path, command, argument, or endpoint.
• Native setup requires a catalog-pinned version 2 release manifest with the exact setup executable path, size, and SHA-256. SessionDock compares that identity with the locked extracted file and complete internal inventory before both phases.
• The embedded compatibility catalog now recommends the independently verified immutable HandleScope 0.3.0 release. Automatic, Keep installed, exact runtime, and automatic/v1/v2 API choices remain unchanged.
• Reviewed HandleScope 0.1.4 and 0.2.2 selections retain their fixed Windows PowerShell RemoteSigned adapter for backwards compatibility. Native setup does not invoke PowerShell or change execution policy; neither path elevates, silently installs, downgrades, or enables the integration.

SessionDock 2.8.0

SessionDock 2.8.0

Dynamic HandleScope compatibility

• SessionDock and HandleScope can now evolve together through a signed, rollback-resistant compatibility catalog. HandleScope 0.2.2 is the new automatic recommendation, while v0.1.4 remains a supported legacy fallback. Choose Automatic, Keep installed, or an exact reviewed release, plus automatic, v1, or v2 API compatibility.
• Opening the integration panel and selecting Refresh remain local-only. The new explicit Check versions action retrieves and verifies the catalog; checking or changing a preference never installs, replaces, starts, stops, upgrades, or downgrades software.
• Installation remains a separate confirmation for the selected release. Exact package, checksum, optional release manifest, API executable, ZIP layout, and internal inventory checks remain mandatory, and SessionDock refuses every downgrade and silent integration opt-in.
• Newer HandleScope releases negotiate authenticated metadata against the signed catalog and can select only SessionDock's compiled v1 or v2 endpoint adapter. Remote metadata cannot supply code, commands, paths, or endpoints.
• Existing handlescope.json opt-ins and the exact five-field connection.json discovery format remain compatible. The reviewed v0.1.4 runtime retains its metadata-404 legacy v1 fallback, while version/API preferences are stored separately.

SessionDock 2.7.6

SessionDock 2.7.6

Reliable HandleScope installation

• Managed setup is now pinned to the newly published immutable HandleScope v0.1.4 release, whose contract explicitly authorizes the separately confirmed standard-user install, start, and autostart flow. Confirmation now discloses that an older supported per-user install may be replaced; integration opt-in remains separate.
• The verified HandleScope v0.1.4 installer now works with Windows' default Restricted PowerShell policy by using RemoteSigned only for the checked child process. SessionDock still never uses Bypass or Unrestricted, changes saved policy, overrides Group Policy, elevates, or enables the integration automatically.
• Exact pinned GitHub assets delivered without a Content-Length header are now validated instead of rejected early. Declared length mismatches, incorrect body sizes or hashes, checksum failures, unsafe ZIP layouts, and internal inventory changes still fail closed.
• Installation failures now show a localized safe category and the official setup guide, making policy, network, integrity, environment, and lifecycle problems actionable without exposing internal details or running unverified code.
• Release packaging now handles competing file-system creation safely before immutable artifact verification.

SessionDock distribution hold — 2026-08-04

Distribution withdrawn — 2026-08-04

Do not download, restore, allow, or run current SessionDock binaries from mirrors, Discord attachments, browser caches, or another computer. Do not disable Microsoft Defender or add an exclusion.

A separately shared unsigned integrated-test executable using SessionDock's retired compressed single-file layout was detected as Trojan:Win32/Wacatac.B!ml after an Internet-origin download. Its SHA-256 is 8041C3268B698A2F964654B7B0C5F67BC2B2B1035E44AB767D9074F498612B28. The Discord bytes exactly matched the local development artifact, ruling out byte-level transport modification, but Microsoft has not yet determined that the detection is incorrect.

The former canonical v3.0.0 assets were not the exact detected development file. They were withdrawn because they were also unsigned, used the same heuristic-sensitive packed layout, and do not meet the new trusted-publisher release gate. The former Setup SHA-256 was 04CCFF322788E3E9954C1DF5CB57CD156E26253BE7B6B093FA151273050DD6AA; the former portable ZIP SHA-256 was 410E5C9C453BB1768E06CABC5951D1C1A75517599395302CFB0DECB3F282DDE4.

No executable or package is attached to this security notice. The v3.0.0 source tag remains for audit. A replacement will be published only after transparent multi-file inventory verification, trusted Authenticode signing and timestamping, ExactWheel provenance/licensing approval, Defender review, staging, attestation, and public re-download verification all pass.

See the repository security policy and docs/DEFENDER_DETECTION_RESPONSE.md before handling any saved copy.

SessionDock 2.7.5

SessionDock 2.7.5

One-click search clearing

• Account search and Recent and Favorites search now each provide a dedicated clear button beside the field.
• The buttons appear only for an active query, return keyboard focus to the search field after clearing, and include localized accessible names and help text in every supported language.
• HandleScope remains optional and pinned to v0.1.3; its confirmed installation runs as the standard user and does not enable the SessionDock integration automatically.

SessionDock 2.7.4

SessionDock 2.7.4

Visible keyboard focus and automatic release announcements

• Closed account, language, sound, batch, and history selectors now show a clear keyboard focus ring that follows dark, light, and Windows high-contrast themes.
• A regression contract protects every production selector that inherits the shared ComboBox style.
• After a verified GitHub release becomes public, Bota now posts the canonical release notes automatically. A read-only preflight validates the bot identity, channel, role, effective permissions, and release history before staging, while deterministic receipts and message verification make retries safe.
• HandleScope remains optional and pinned to v0.1.3; its confirmed installation runs as the standard user and does not enable the SessionDock integration automatically.

SessionDock 2.7.2

SessionDock 2.7.2

One-click HandleScope installation restored

• Restored the localized Install HandleScope v0.1.3 button in the integration panel while keeping the pinned official setup guide available.
• Pinned the installer to the immutable canonical v0.1.3 Windows x64 package and checksum, with exact size and SHA-256 verification, safe ZIP extraction, and full internal inventory validation before anything runs.
• The confirmed standard-user install starts the HandleScope API and enables its limited per-user autostart without elevation or a PowerShell execution-policy bypass.
• Installing HandleScope does not enable the SessionDock integration automatically; Enable remains a separate explicit choice.

SessionDock 2.7.1

SessionDock 2.7.1

Complete localization and clearer recovery guidance

• Added complete live display-language support for English, Dutch, German, French, and Spanish, including runtime-generated messages, confirmations, validation, accessibility names, and progress states.
• Restored HandleScope v0.1.3 compatibility: each one-time plan ID from the preliminary check is forwarded only to its matching execution request.
• Aligned the HandleScope lifecycle boundary with its immutable v0.1.3 contract: SessionDock no longer downloads, installs, updates, uninstalls, starts, or configures autostart for HandleScope and never requests elevation for it. The integration opens the pinned official setup guide and accepts only the exact published v0.1.3 API executable.
• Upgrading leaves any existing HandleScope installation, running process, autostart choice, and SessionDock opt-in unchanged. Manage the lifecycle and autostart through HandleScope's own scripts, and manage the opt-in in SessionDock's integration panel.
• Localized batch retries, running-client management, diagnostics, metadata transfer, integrations, Auto-Join, updates, sounds, and account or history workflows.
• Added locale-aware bundled release notes. When an older translation is unavailable, SessionDock clearly labels the English fallback.
• Strengthened localization checks for missing keys, format placeholders, singular and plural messages, hard-coded interface text, live switching, and accessibility metadata.
• Replaced raw internal failure details in user-facing workflows with localized, actionable guidance while preserving technical identifiers that users may need.

SessionDock 2.7.0

SessionDock 2.7.0

Faster workflows, safer sharing, and better access

• Search saved accounts and Recent or Favorite experiences from the current workspace. Ctrl+F focuses search, Escape clears it, and matching includes account groups, names and IDs, destinations, places, and tracked servers.
• Organize accounts into groups, select a group for batch launch, save named presets with remembered delays, and retry only accounts that failed. Starting a batch or retry still closes running verified Roblox Player clients.
• Explicitly watch a Roblox user with the selected account and automatically start Player when Roblox reports a usable current server. Player makes the final access check. The memory-only watch checks at a bounded rate, backs off when Roblox asks, remains cancelable, expires after four hours, and makes at most one Player start attempt.
• Change the display language between System default, English (United States), and Dutch (Netherlands) without restarting. SessionDock also remembers a safe visible window size and position, and now has its own icon in the app, executable, taskbar, Alt+Tab view, and installed shortcuts.
• Review, copy, or export a privacy-safe support summary from About and diagnostics. It includes bounded system and component states and counts, but excludes logs, paths, account details, destinations, browser data, cookies, and tokens, and is never sent automatically.
• Export and import reviewed safe metadata for account appearance, groups, ordering, and pinned public Favorites. Roblox user IDs match accounts that already exist locally; sign-ins, cookies, destinations, private-server details, tracked servers, and browser profiles are never transferred.
• Optionally enable Open with SessionDock for supported official Roblox links. It does not replace Roblox's default handler, validates every incoming link, hides private codes, lets you choose an account, and asks for confirmation before launch. Private incoming links are not saved.
• Improved keyboard and screen-reader support with proper selectable controls, clearer names and help, live status and error announcements, and state cues that do not rely on color alone.

Some runtime confirmations and detailed technical previews may still use the English fallback. The optional link handler is off by default, and SessionDock does not automatically send diagnostic or metadata files.

SessionDock remains unsigned, so Windows may show Unknown publisher. The bootstrap Setup keeps its existing installer icon to preserve update compatibility with earlier SessionDock releases.