A clear path to
your first connection.
Practical guidance for a trusted Windows workspace.
Getting started
Install and launch
- Download the official Windows x64 installer and verify its checksum.
- Fully exit any running Godesk copy, including the tray process, before installing or upgrading. Run the installer on both computers. If your distribution requires an installation password, obtain it from the developer or your administrator; it is not published here.
- Open Godesk Connect and confirm peer services are ready in Settings.
Network prerequisites
Begin with two reachable Windows computers on a trusted local network. Your administrator may need to allow the app through the firewall or configure routes between networks. Do not disable security protections to make a connection work.
Each device has its own local identity and profile. Do not copy application profiles or private identity material between computers.
Connecting devices
Discovery and Remote ID
Use Directory to find reachable devices, or enter the other computer’s Remote ID in Quick Connect. Discovery helps find an endpoint; it does not grant access or bypass firewall policy.
Recent computers and multiple tabs
Recent computers remembers successful remote sessions and provides Reconnect. Reconnection does not bypass host approval. Multiple device tabs keep outgoing sessions separate; remote input and clipboard actions follow the selected approved tab.
Pairing and permissions
Confirm you are pairing with the intended computer and verify the identity shown by the app. Request remote assistance; the host chooses what to approve. A paired device is not automatically entitled to screen viewing, keyboard input or file access.
For routed networks, ask your administrator to configure supported reachability. A website address does not act as an internet relay.
Chat, calls & sharing
Chat
Open a conversation with a trusted reachable peer. Messages and conversation history are stored locally. A chat conversation does not itself grant remote-control permission.
Voice calls
Call an eligible approved contact. The recipient must answer before audio opens. Use mute or Hang up in the call window. Use working default Windows input and output devices; a headset helps reduce echo.
Files and folders
Use chat attachment actions or the supported session sharing flow. Confirm the receiving location and required permissions. Use compatible builds on both endpoints.
Display and session tools
In a remote session, select an available display, use Fit to Screen or Actual resolution, and enter or leave full screen. Session chat keeps the conversation available during assistance. These tools do not grant input permission.
Clipboard sharing
Enable sharing only with the intended peer and required approval. Supported text, images, files and folders follow the active remote tab. A new copy and paste may be needed after enabling sharing; avoid copying sensitive data during a shared session.
Administration & client views
Admin Mode
Authorized administrator mode exposes protected configuration controls. Ask the person responsible for the installation for access; no administrator credentials are published in this documentation.
Client-facing visibility
Client-facing use follows configured profile, sharing and directory visibility controls. Some device details can be hidden in these views. Display privacy is not network-address secrecy.
Background and Windows sign-in
Settings can keep the app running in the system tray after its window closes and optionally launch it after your Windows user signs in. Fully exiting the app stops connectivity. This is not a pre-login service or unattended-access grant: the PC must be awake and connected, and incoming remote assistance still needs approval.
Verified app updates
Settings supports importing verified update packages and using a configured trusted update source. Package signature and integrity checks are separate from Windows Authenticode signing: the publicly listed setup EXE remains unsigned. A website download does not configure an update source automatically; follow your administrator’s update policy.
Configuration
Use Settings to review device sharing, trusted peers and network options. Choose Light, Dark or System appearance, adjust desktop notifications, or enable automatic directory refresh. Follow your organization’s network policy. Administrator mode does not replace the recipient’s consent for a remote desktop session.
Access & privacy
Godesk uses verified device identities, pairing and encrypted peer communication. Remote assistance requires explicit host approval. End the session or revoke control when work is finished; use Blocked Users to manage unwanted users.
Keep paired devices and Windows accounts protected. Review what you share through chat, files, clipboard and directory fields. Local-first does not mean immune to compromise.
App communication and website hosting are separate. The website does not grant remote access, and installation passwords are not remote-session authorization.
Troubleshooting
Device not found or connection failed
Confirm both apps are running, discovery is enabled where appropriate, and the computers are reachable. Check your intended Remote ID, current app versions, configured routes and administrator-approved firewall rules.
Pairing problems
Confirm device identity with the other person. A changed identity may require a new verification. Do not accept an unexpected identity just to silence a warning.
No audio
Confirm the recipient answered, the call is not muted, and Windows has working default microphone and speaker devices. Check device selection and microphone permissions yourself. Try a headset.
Remote input does not work
Screen viewing and control are separate approvals. Ask the host to review input permission. Windows secure desktop and integrity-level restrictions still apply; do not bypass Windows protections.
Report a bug
Open Help & Feedback in the app. Report a Problem, Suggest a Feature, or compose General Feedback. Preview, copy, or save the report; Open Gmail Draft prepares a message that you review and send yourself. Screenshots must be attached manually in your email app. Optional diagnostics are not automatic submission. Include the app version and reproduction steps, and review the report before sending.
Frequently asked questions
Is Godesk Connect free?
The beta installer is publicly available to download. No pricing, commercial-use rights, or perpetual free license are promised here; review the applicable software terms before organizational use.
Do I need a cloud account?
No mandatory cloud account is required. Reachable peers communicate directly, and conversations are stored locally.
Does it work over the internet?
The app focuses on local and configured routed networks. This public website does not enable internet-wide remote access. Routing, firewall policy and app configuration determine reachability.
Can someone control my PC without permission?
Knowing a Remote ID does not grant access. Remote desktop requires identity verification, pairing and explicit host approval. You can revoke control or end the session.
Which Windows versions are supported?
The installer targets Windows x64 on Windows 10 or later. That installer target is not a claim that every Windows edition has been physically tested. Verify your organization’s Windows version, network policy and audio hardware before depending on a session. macOS and mobile installers are not available here.
Where can I report a bug?
Use Help & Feedback inside the app to preview, copy, or save a report, or open a Gmail draft. Save a local .eml draft with your screenshot attached and send it through a compatible desktop mail client. Browser Gmail requires manually attaching the image; the app does not automatically submit feedback. Do not include passwords or sensitive conversations.