Tighter access to devices, sessions and executors

A device's live screen now reaches only its owner and the run or chat that holds it, and the executor on your machine refuses every tool outside Tessa's list.

Diagram: the live screen of a private Android device reaches its owner and the run or chat that holds it, while other members only see that it is unavailable. Below, the Tessa Executor runs tap, type, swipe and screenshot, and refuses shell, file system and clipboard.

We work on security continuously, and most of it ships without a line here: updated dependencies, hardened builds, stricter checks of uploaded apps. This release also ends a removed member’s open sessions at once, and private devices show their installed apps only to their owner.

Also in this release

Tessa files or edits an issue from the chat only after a further message from you confirms it.
In a chat on a desktop computer, every turn starts with the three-second countdown a run shows.
Feedback screenshots are visible only to the person who sent them.

Tighter access to devices, sessions and executors

Start your free 14-day trial