Skip to content

SessionDock 3.1.2

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Aug 19:09
· 2 commits to main since this release
Immutable release. Only release title and notes can be modified.
0e257dd

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.