Chrome plugin tutorial

The Chrome plugin lets Nexts use the real, signed-in Google Chrome on your computer. Choose it for tasks that depend on existing accounts, tabs, cookies, or browser extensions, such as reviewing dashboards, filling forms, organizing tabs, and researching across websites.

1. Install both parts

1. Open Plugins / Skills in Nexts, find Chrome, install it, and leave it enabled. This prepares the local Chrome Control connection.
2. Open the Nexts AI extension in the Chrome Web Store and select Add to Chrome.
3. Open chrome://extensions and confirm Nexts AI is enabled. Pinning it to the toolbar makes its status easier to inspect.
4. If Chrome or Nexts was open during installation, restart both, then start a new Nexts conversation.

The extension discovers Nexts through a local connection. There is no pairing code to copy, and you should not expose the local connection port to a LAN or the internet.

2. Complete a first task

Choose the Chrome plugin from the input menu in a new conversation, then state the goal, website, and stopping condition. For example:

• “Use Chrome to open my signed-in project dashboard and summarize this week's anomalies. Do not change anything.”
• “Compare prices and delivery times across the three supplier pages I already opened, then make a table.”
• “Fill this form, but stop before submission so I can review it.”
• “Organize the research tabs in this window by topic and keep the pages used in the final result.”

Nexts works in task-specific tab groups where possible so your active browsing is not taken over. It asks you to take over for sign-in, CAPTCHAs, or pages that require human judgment.

3. Approve sensitive actions

Sending data, submitting forms with external effects, uploading or downloading files, and entering sensitive information require confirmation. You can allow once, allow for the session, or deny.

Start with a read-only request and specify a stopping point such as “stop before submission,” “do not send,” or “do not download.” Review payments, deletions, publishing, and account-security changes one by one.

Chrome versus the in-app Browser

• Use Chrome when the task needs your real browser's signed-in state, tabs, cookies, or extensions.
• Use Browser for local web testing, localhost, or work that should not touch personal Chrome state.

Troubleshoot the connection

1. Confirm you are using Google Chrome 116+, not Edge, Brave, or another Chromium browser.
2. Confirm the Chrome plugin is installed and enabled in Nexts.
3. Open chrome://extensions and check that Nexts AI is enabled and shows no error.
4. Fully quit and reopen Chrome and Nexts, then test in a new conversation.
5. On managed devices, ask the administrator whether the extension and local Native Messaging are allowed.
6. If it still cannot connect, reinstall the Chrome plugin in Nexts, then reinstall the Web Store extension.

Browser page content is not stored as account-profile data by the Nexts account service. Content required for a task may still be processed by the model provider you selected, so follow that provider's data policy and grant only the access the task needs.