Remsup

Windows remote support

Remote support.
Human permission.

A visible Windows app for authorized maintenance. Connect a support operator or an AI agent, with controls that stay in the device owner’s hands.

Explore the source Read the setup guide

MIT licensed Windows x64 MCP integration

The support connection
01 / Device ownerVisible Windows app
Authorized sessionConfigured relay or direct LAN
02 / Support operatorPerson or AI agent
CommandsScreenMCP tools
Connection overview. Infrastructure and access are configured by your administrator.

Built for support

A clear task. A visible session.

Run maintenance commands

Authorized operators send bounded commands and receive results with execution time and output limits.

View and control the screen

Screen capture, mouse and keyboard control follow the receiving device’s settings, consent policy and session expiry.

Keep local controls close

The owner can stop support and exit from the tray. Unattended access requires explicit device-owner authorization.

For AI operators

Your agent.
A defined support task.

Remsup exposes authenticated MCP tools for authorized support work. Connect your agent to an administrator-provisioned endpoint and use the support skill to follow the documented workflow.

Explore the operator skill
  1. Authorize

    Agree on the device and the maintenance task.

  2. Connect

    Use configured infrastructure and protected credentials.

  3. Verify

    Check command results and close screen sessions when finished.

Before your first session

Read the setup.
Set the boundaries.

This is a source distribution for controlled testing. Bring your own configured infrastructure and review the security model before use.

Read the security notes
What do I need to run Remsup?

Windows x64 and the separately installed Evergreen WebView2 Runtime. Build the single Windows EXE from source using the prerequisites in the README. No hosted relay, update service or release executable is supplied with the source snapshot.

Build prerequisites
Does closing the window end support?

No. Closing or minimizing the window can keep support running in the tray. Use Stop support to end receiving support, or tray Exit to close the application.

How does owner consent work?

Work requires device-owner authorization. Screen access follows the receiving device’s settings; automatic approval after pairing can be enabled. Do not assume every command or screen action prompts the owner. Windows administrator elevation remains a local owner action.

Can an operator change Remsup settings?

Remote editing of ordinary settings is OFF by default. It requires local owner opt-in and an authenticated screen-control session, and is limited to specified settings. Permission changes, credentials, firewall and administrator actions remain local.

Permission details
What should I know about the security model?

Windows relay and LAN connections use TLS with a verified certificate pin. The relay administrator can inspect relayed data; this is not end-to-end encryption. The source snapshot is not production security approval. Review the security documentation and provision your own endpoints.