Get NEXUS access
NEXUS is invite-only. Use the private access link issued to you and complete the account setup before installing anything.
Start with setup, learn what each page is for, or jump straight to the problem you are trying to fix.
Following the same order avoids most pairing, profile and Run Center problems.
NEXUS is invite-only. Use the private access link issued to you and complete the account setup before installing anything.
Sign in, open Machines and download the current Windows Agent. Install it on the PC that will run your browser sessions, then keep it running while you use NEXUS.
Open Machines → Pair PC, create a one-time pairing code, then enter it in NEXUS Agent. Pairing codes expire after 10 minutes.
Open Profiles and create an Amazon browser profile on the paired Windows PC. Each profile keeps its own local browser state and configuration.
Start the profile and complete the normal account login in the local browser. CAPTCHA, OTP, passkeys and verification challenges stay manual.
Open Run Center, choose the PC and profiles, then use Light, Normal or Deep — or select one of your saved custom templates.
Each dashboard page has one clear job.
Pair PCs, check Agent status, see versions and health, rename devices and open Agent controls.
Open Machines →Create and manage persistent browser profiles. Start a profile for manual login or verification, and use Download cookies when you need a secure JSON export of that profile’s current cookies.
Open Profiles →Select profiles and choose Light, Normal, Deep or a saved custom template. Follow active or scheduled runs here. Custom templates use Browse and Pause durations, with wishlist and cart limits mixed into browsing. The full guide below explains limits and reordering.
Open Run Center →Follow profile, automation and Agent events. Open a Needs attention card on Dashboard for details and the next step. Clear hides older events for the selected PC in this browser, including Dashboard and other open tabs. It does not delete stored history or stop tasks; new events remain visible.
Open Activity →Find your NEXUS ID, Telegram link status, active sessions and emergency recovery options.
Open Settings →Choose Standard for a ready-made mode, or Custom to use a template you saved. The mode descriptions below are the same ones shown in Run Center.
Use an online, paired PC.
Choose profiles on that PC.
Standard or a saved template.
Readiness checks run first.
Follow progress and any alerts.
NEXUS checks the browser engine, profile, proxy, login/verification state and PC resources. If a required check fails, the run is blocked instead of starting in a bad state.
Moves around Amazon by scrolling, opening product pages, running broad searches and returning to the marketplace home page.
Opens a product page and attempts Add to Wishlist. If the profile is logged out or needs manual verification, NEXUS skips the action.
Opens a product page and attempts Add to Cart. Manual verification challenges stop that cart action instead of forcing it through.
Takes a short 8–20 second pause between interaction batches. Pauses are mixed into browsing automatically.
All modes scroll, explore product pages and run searches. NEXUS randomly alternates these actions with wishlist or cart activity and brief 8–20 second pauses.
Mostly scrolls and explores products, with occasional wishlist activity. Does not add items to the cart.
Balances browsing with occasional wishlist and cart additions.
Includes more wishlist and cart activity, with longer browsing blocks.
Limits apply to each profile for one run. Browsing blocks repeat within the duration you set; after an item limit is reached, browsing continues. Random selection means a run may add fewer items than the limit.
If an addition cannot be confirmed, its allowance is reserved and the action stops instead of trying again. Check the profile before starting a new run.
Login and verification challenges need your attention. NEXUS never checks out.
These numbers are relative random-selection weights, not item counts or percentages of running time. When a wishlist or cart limit is reached, its weight moves to browsing; brief pauses do not become more frequent.
Illustrative example only. Action order and timing vary, and a run may add fewer items than the limits. NEXUS never checks out.
Dashboard popups use plain-language messages such as “Start request sent” or “Stop request sent”. This means your request was accepted, not that the action has finished. Follow progress in Run Center or Activity. If a request cannot be sent, the popup tells you to check your PC and the page message. You can dismiss a popup; sent requests disappear after 8 seconds, while errors stay until dismissed.
Open the issue that matches what you see. If it still fails, Activity usually gives the best timestamp and event context.
The loading screen checks your sign-in, then loads your PCs, profiles and activity. It closes as soon as the workspace is ready. If loading takes longer than usual, check your connection and use Reload page when it appears. Reloading the dashboard does not stop automations on your PC.
Make sure NEXUS Agent is running on that Windows PC and the PC has internet access. Then open Machines and refresh. If it stays offline, restart the Agent once.
Create a fresh pairing code from Machines → Pair PC only if the Agent says its device connection was revoked or invalid. A compatible Agent keeps pairing during a temporary access-check failure, stops local work safely and waits for access to return. Stopped runs do not restart automatically.
The Agent reserves that attempt’s item allowance and stops the action rather than retrying an uncertain addition. Review the local wishlist or cart before starting a new run. An item limit is a maximum allowance, not a promise that every item was added.
Generate a new code, copy the complete value and use it before the 10-minute expiry. Confirm you are pairing the intended Windows PC.
Open the profile locally and complete the site login or verification. When the profile is signed in again, return to Run Center and retry.
Check that the selected PC is online, the selected profiles belong to that PC and none of them needs login or verification. The Start button stays disabled until the required setup is valid.
Open Run Center → Custom. Only templates you saved yourself appear there. Light, Normal and Deep are Standard modes and do not appear in the custom-template list.
Add at least one Browse step and make sure your PC reports item-limit support. Agent 1.9.13 adds this support. A dashboard update alone does not update the PC. Old saved wishlist/cart durations are no longer used; review the Browse durations and save your template again.
Check the proxy host, port and credentials and confirm it is assigned to the correct profile. If the proxy provider changed the credentials, update the profile before retrying.
Update NEXUS Agent to version 1.9.12 or newer, make sure the paired PC is online, then reopen the profile actions and try Download cookies again.
Use the same Telegram account the access was issued for. Group-member access may require a fresh membership check; targeted access should match the Telegram ID it was issued to.
Use only the official NEXUS installer or update path. Do not install Agent builds from third-party links or unknown files.
The important account information lives in Settings.
Your permanent account identifier. Keep it available when reporting an account-specific problem.
Where shown, choose Continue with Telegram to open your existing linked account without entering an account ID. Use Sign in or recover for account-ID approval or your optional backup phrase. Telegram sign-in does not create an account or bypass membership checks.
You can configure a 12-word backup phrase in Settings. Keep it private — support never needs the phrase itself.
Do not send passwords, proxy credentials, your 12-word recovery phrase, cookies or Agent device credentials. A screenshot, PC/profile name and approximate time are usually enough to investigate a problem.
Message @trymex116 with what you were trying to do, the affected PC or profile, the visible error and roughly when it happened. A screenshot is useful. Never send passwords, proxy credentials or your recovery phrase.