Where Esper is going. And where it isn't.
The scope contract, published. Every feature lands in one of four lanes, and the last lane matters as much as the first: if something is not on this page, it is not planned.
01Planned
12Wanted and written down, waiting for a reason to start.
QR-code pairing
Point a camera at the screen instead of typing the code.
FIDO2 on connect
An optional hardware-key second factor. Keys already make passwords unnecessary, this hardens the key itself.
Key rotation
Rotate a device key without re-pairing every peer.
Session handover
Transfer a live session to another technician.
Co-browsing
Embed Esper in your web app so support, human or an AI over MCP, sees a user's page and the errors behind it. Consented, masked by default, on your own relay.
Phone as host
Share an Android screen out, not just control from it.
AV1 encoding
Needs hardware support on both ends before it earns its place.
TCP fallback
Control-only sessions on networks that block UDP entirely.
Searchable recordings
Session recording with an index you can actually search.
Remote printing
Genuinely useful, genuinely fiddly on three platforms.
On-screen annotation
The one conferencing-adjacent feature with a real support use.
Traffic padding
Blunting traffic analysis. Named in the threat model rather than glossed.
02Building now
10Designed for from day one, landing in the 1.x releases.
Signed installers
Code-signed and notarized builds, so first launch stops warning.
Opt-in update alerts
One anonymous request that fetches a version number and nothing more. Off until you turn it on.
Android and iOS
Your machines, from your pocket. Clients first.
Hardware-accelerated encoding
1.0 is software-only by choice. GPU encoders come next.
Several people in one session
Many viewers, one controller, explicit handover.
Session recording
Local, controller-side, and visibly indicated on the host.
Remote power controls
Reboot and reconnect, lock, logoff, and Wake-on-LAN on the same segment.
Quality of session life
Change the remote resolution, suppress wallpaper, pause a session, block host input with a local override.
Device groups and file box
Organize a fleet locally, and a shared drop area for files.
In-session chat
Text chat while a session is live. Nothing persistent.
03Working today
8Built and running in the current early builds.
Remote control
View and control with multi-monitor switching and several sessions in tabs.
Pairing by key
One short code, then cryptographic keys forever. Invite links for guests, unattended grants for your own machines.
The connection ladder
Local discovery, VPN detection, direct connections, and your own broker and relay.
Quality presets
Text, balanced and motion, plus automatic content detection. The cursor renders locally and never lags.
Files and clipboard
Drag and drop, a two-pane file manager, and clipboard sync for text and images.
Consent built in
A session indicator the controller cannot hide, a panic key, privacy screen, and lock on session end.
Terminal and headless
A shell on any paired machine, including servers with no display at all.
Agents over MCP
A built-in MCP server with scoped grants, on-screen confirmation and a local log.
Deliberately not
4Saying no is a decision. If it is not on this page, it is not planned.
Accounts or a cloud directory
The entire point. No server means no directory, no database of you.
Meetings, video or VoIP
That is a different product. You are already on a call with whatever you prefer.
Persistent contact chat
A messenger needs the directory Esper refuses to run.
Clipboard sync for files
A paste that silently becomes a file transfer would defeat the transfer permission.
This page tracks intent, not dates. The full scope contract, feature by feature against TeamViewer, lives in the repository, and the issues are where lanes change.