Set up Gelyx.
A quick guide to what lives in Gelyx and what stays on your computer.
1. Sign in with Discord
Use the Discord account you intend to keep. Your records and linked computers belong to its private workspace. Customer tools require active owner-assigned test access while checkout is closed. Ask the site owner for access before pairing; sign-in and downloading do not grant a trial.
2. Connect your computer
After the owner assigns active test access (the owner account is exempt), open Machines and name your Windows PC. Create a pairing code, then enter it in the separate Gelyx Windows connector on that same PC. The code expires in five minutes. Keep it private.
Sign in and open Download Connector for the unsigned Windows testing preview. All signed-in users can download and install, including accounts with no tier. An active tier is required to pair or connect; the owner is exempt. Do not disable Windows security protections or download from an unverified link.
3. Save your client paths
Under Machines, open the computer’s Client settings. Select the client, set its EXE or JAR path and working directory, and provide the Java executable if needed. Paths refer to that Windows PC—not the Gelyx server.
Arguments are literal entries, one per line. Never enter passwords, tokens or proxy credentials there. File verification checks paths only; it does not launch a client or prove compatibility.
4. Organize your records
Use Account Manager, Mailboxes and Proxies to save private records. Secret fields remain hidden until you explicitly reveal them. In an edit form, leave a secret blank to keep it, or choose Clear to remove it. Saving these records does not change credentials at an external service.
5. Review the testing workflow
Use Account Manager → select accounts → Start → saved task to review an experimental account task, the chosen PC/profile and proxy. Each run requires explicit local approval in the Connector. Real automatic login, proxy use, fresh stats and task completion are not yet verified; this is controlled testing, not a finished service. Runs reports observed progress and failures, not assumed success.
Profile-only Launch approval is different: it starts the saved client without account credentials or a saved proxy. For Microbot status and Tier 2+ locations, choose Monitor mode in a supported Connector preview and approve the profile locally. Check the exact version on Downloads; installing a preview does not prove a workflow works.
Scheduled execution, browser migration, direct client imports and new mailbox provisioning remain unavailable. Historical Studio tasks are not automatically replayed. Customer plans never include marketplace tools.
If something doesn’t work
For an expired pairing code, create a new one. For a form-verification error, return to the page and reload it before submitting again. For a conflicting edit, reopen the latest record. Don’t share screenshots of revealed passwords, pairing codes or tokens.