Skip to content

feat(desktop): ask once what other devices may do on this computer - #7454

Merged
reachjalil merged 1 commit into
devfrom
feat/ask-to-allow-this-computer
Nov 17, 2026
Merged

reachjalil merged 1 commit into
devfrom
feat/ask-to-allow-this-computer

Conversation

@reachjalil

Copy link
Copy Markdown
Member

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.tsx reads 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.
  • A split button made from the existing button and dropdown menu: Allow all tasks first, Allow starting tasks behind the arrow. Keep it off stores "Nothing".
  • A level the organization or the app cannot take is listed locked with its reason, and the button starts on the next one. No card when nothing can be allowed.
  • Either answer is stored as the owner's choice through the existing bridge, so the card does not return.
  • Shown only under remoteTasksOptIn; no new flag.

What else changed?

  • lockedReason and the query key are exported from the Settings section, so both places share one rule and one cached read.
  • The feature doc describes the ask.

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.
  • The doc's screenshot is a local render of the card with stand-in state. No end-to-end spec drives a real desktop through it.

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>
@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openwork-app Ready Ready Preview Nov 16, 2026 11:59pm UTC
openwork-den Ready Ready Preview Nov 16, 2026 11:59pm UTC
openwork-landing Ready Ready Preview, v0 Nov 16, 2026 11:59pm UTC

Request Review

This branch was successfully deployed

3 active deployments
Preview – openwork-app — 3c4d2626 Deployed Nov 16, 2026 by vercel[bot]
Preview – openwork-landing — 3c4d2626 Deployed Nov 16, 2026 by vercel[bot]
Preview – openwork-den — 3c4d2626 Deployed Nov 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant