Repository navigation
feat(desktop): ask once what other devices may do on this computer - #7454
Merged
Merged
Conversation
With the organization's opt-in, a computer takes nothing from its owner's other devices, Workbot or agents until the owner allows it, and the only place to allow it was Settings > Devices. Nothing told the owner, so computers stayed off without anyone having decided that. A signed-in desktop whose owner has not chosen now shows one card above the composer. Its button allows all tasks, an arrow beside it switches it to starting tasks only, and Keep it off records that instead. Either answer is the owner's choice, so the card does not return. A level the organization does not allow is listed locked with the reason. Signed-off-by: Jalil <reachjalil@gmail.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this about?
A signed-in desktop now asks its owner once, above the composer, whether Workbot and their other devices may work on that computer.
What problem does it solve?
With
remoteTasksOptIn, a computer takes nothing from other devices until its owner allows it. The only place to allow it was Settings › Devices and nothing pointed there, so computers stayed off without their owners having decided anything, and tasks sent to them were refused.What was the situation before?
The owner had to know the setting existed. A refused task never reaches the computer, so nothing appeared on it either.
How is this implemented?
remote-access-ask.tsxreads the same access state as Settings › Devices and shows the existing composer notice card while the opt-in applies, the computer is connected and no choice is stored.remoteTasksOptIn; no new flag.What else changed?
lockedReasonand the query key are exported from the Settings section, so both places share one rule and one cached read.Release note
Where your organization requires it, OpenWork now asks once whether Workbot and your other devices can start and manage tasks on this computer.
Evidence
apps/app/tests/remote-access-ask.test.tsx: no ask anywhere → the card asks, and each answer is saved and ends it.