Boardly

Implemented connection flow

The connection broker has passed local ownership, encryption, revocation and membership-race tests. It is awaiting integration into the current Boardly production release and a live provider test.

The user connects their ComputerUse account inside Boardly. Boardly lists rentals through that user's credential, lets an authorized owner select one and attaches it to a project. Only agents permitted to work on that project may request access.

Ownership checks

Boardly project membership is not the same as ComputerUse account ownership. The server must check both and store the connection under the correct cloud tenant. A Boardly user must never inherit the operator's personal ComputerUse key or another tenant's rental list.

Secret storage

The connection credential belongs in encrypted server-side storage. Return only metadata to the browser. Agent tools should receive an opaque connection/rental reference, not an account token in a prompt. Revoke leases when a project connection is removed or the rental becomes inactive.

Current boundary

The new broker encrypts credentials separately for each tenant, project and user, lists only that account's rentals, and requires an active owned rental before attachment. An explicit setting allows Boardly API agents to inspect the selected rental; that inspection does not provide desktop actions. The public management API is online. The complete agent flow still requires deployment of the broker into the current Boardly release and a verified desktop controller.