Skip to content

thread0 0.1.266

Choose a tag to compare

View all tags
@david-maidepot david-maidepot released this 21 Sep 15:02
· 1 commit to main since this release
v0.1.266
5975417

thread0 0.1.266

This release updates collaboration with outside developers, adds group rooms, and includes changes prompted by real-device reports. User live validation remains pending.

Collaborators at scale

  • The collaborators screen on the PC and the owner's phone is now a people list instead of a dropdown: people with unread messages first, then most recent conversation, each row with name, role, last message, time and an unread badge. The sidebar badge is the sum of unread messages and clears when you read on either device — the PC device record is the single source of truth.
  • A collaborator's message notifies the owner with an OS notification on the PC (skipped while the window is focused) and a push on the owner's phone. The owner's reply pushes only to that collaborator's device, including observe-role devices. The notification can be switched off in Settings on both the PC and Remote.
  • Session headers show who is looking at the same session (based on shared sessions and recent activity), without any polling.

Group rooms

  • The owner creates rooms and picks members from the active collaborators; a room can be any subset and there can be several rooms. Members see the room in the conversation picker, messages carry the sender's name, and every member device is pushed when someone posts (the sender excepted). Removed members stop receiving immediately and non-members are refused without learning the room exists. Observe-role collaborators can talk in rooms they belong to.

Changes prompted by real-device testing

  • Collaborate-role guests could not create a folder, pick an additional folder or start a session in their own folder. The guest's folder lives under Documents\AgentDeck\guests, outside the PC owner's browse roots, and the registration, creation and browse handlers applied the owner's roots to guests. Those calls are now bounded by the guest scope (shared session folders plus the guest's own folder) and the internal scoped methods cannot be called from a phone. Out-of-scope paths show the collaborator wording ("outside the shared folders, ask the owner") instead of an instruction meant for the owner.
  • The "Accounts this PC allows" list in a guest's new-session sheet labelled the host's accounts as "my subscription"; it now says they are the inviter's subscription in all nine languages.
  • The guest's own-account list reloaded endlessly when the PC's account policy differed from the cloud copy of the invitation. While the PC is reachable it is now the authority for policy and expiry; cloud updates only decide revocation and expiry, and the sheet re-reads access only when the PC changes permissions.
  • Switching a shared session to the guest's own account failed inside the customer PC with "Service request is not allowed", and cancelling failed the same way, leaving the session unable to take input. The desktop's service-request allowlist now includes the execution switch, close and unregister routes, a test compares every route the desktop calls against that list, and a session that restarts under the same id accepts input again.
  • A session view could crash when the collaborator list was unavailable (found by the release gate), and the collaborators panel no longer shows a person's role badge next to a room name.

Update the host PC and refresh Remote to use the matching implementation. Automated fixtures and package checks do not replace real-device acceptance; user live validation remains pending for the collaborator scenarios above.

Downloads

Integrity

The Windows installer is signed with Azure Trusted Signing (MAI DEPOT, Inc); the macOS build is Developer ID signed and notarized. Verify the download against SHA512SUMS.txt before installing.

Assets 2
Loading