To use Nemotron 3.5 Super with a signed-in browser, select a host that serves the exact nvidia/nemotron-3.5-super-120b-a12b API alias and connect a local agent to Tabbit CLI. Ask it to read a preview page's title, environment label, and status, then prepare a release checklist without approving or publishing. NVIDIA announced the 3.5 Super family on October 14, 2026 (release page). A catalog entry for this specific API alias lists text input and text output; verify that against the provider you choose. Keep the separate image-capable Super VL checkpoint distinct. A Reddit tester described uneven results across domain-specific tests, a reason to verify visible page facts instead of asking the model to infer them (discussion).
Key takeaways
This workflow covers text visible in the page using the cataloged text-in/text-out Super API alias. Nemotron 3.5 Super is not interchangeable with the separate Super VL checkpoint.
The model host and local browser tool are separate. Confirm both before you begin.
Start with a preview page and return source URLs beside each value.
Keep the agent away from the approval and publish controls.
A local browser fixture verified session reuse, but no Nemotron inference or model-to-browser integration was run here.
Separate the setup checks
| Layer | What it does | What to verify | Typical failure |
|---|---|---|---|
| Model host | Serves Nemotron 3.5 Super | Exact checkpoint, provider access, a small inference | Alias absent or endpoint unavailable |
| Local client | Runs the agent and browser skill | Skill discovery and permission to launch local CLI | Skill missing or remote-only environment |
| Tabbit Browser | Holds the website tab and login session | Correct site, profile, and visible account | Wrong profile or sign-in prompt |
In this environment, pi --offline --list-models nemotron-3.5-super-120b-a12b found no matching entry. No model call or provider account check was made. The catalog lists Perplexity Agent for this alias, but that does not prove your account can use it. Use the NVIDIA technical report for family details and your chosen host's catalog and logs to confirm the endpoint. Pi's Tabbit invocation is /skill:tabbit; verify the equivalent mechanism in other clients. The Tabbit CLI quick start, complete guide, and Codex setup cover the browser side.
Read a release preview without approving it
Sign in to your staging or preview site in Tabbit Browser. Use an independent task tab and ask for the exact page title, environment badge, visible status, and URL. If the page contains image-only content, stop; a text-only model cannot confirm that evidence. One local Nemotron user described running models inside an orchestrated agent stack, but that setup report does not establish compatibility with Pi or Tabbit.
Inspect the currently open release preview in Tabbit Browser. Do not click approve, publish, or edit.
Return the exact page heading, environment label, and visible release status. Add the page URL after each field. If a value is missing or ambiguous, write unknown.
Prepare a checklist draft named "Nemotron Super Preview Check — GEO-321" with the extracted facts and a blank human-approval line. Do not save it to the release system.
Stop and show me the source page beside the checklist.GEO-321 is an illustrative draft label. It is not a live release or test result. The human reviewer should check that the preview belongs to the intended account and environment, then apply the team's approval rules.
Decide what the model can establish
| Page evidence | Agent may report | Human must confirm |
|---|---|---|
| Visible title and status text | Exact strings with URL | They match the intended release |
| Account/environment badge | Displayed label | The account has the expected permissions |
| Image-only status or embedded diagram | Unknown for this text workflow | Inspect it manually or use a verified VL route |
| Approve/publish control | Its presence and label | Whether the team authorizes the action |
For first use, follow the existing browser connection guide and first-task checklist. If your client cannot run the Tabbit skill, compare MCP and CLI or use the browser agent CLI tutorial. Tabbit Browser is a practical local option when a release page is already open in a signed-in profile. See browsers for AI agents, Playwright browser automation, and browser automation agents for the broader browser-tool context. A parent-run fixture only showed that Tabbit CLI could reuse a signed-in test session; it did not test this model. Read the browser-agent security notes and keep approval human-controlled.
FAQ
Is Nemotron 3.5 Super the same as Super VL?
No. This article covers the text-focused Super checkpoint. Super VL is a separate vision-language model; use it only when your task needs image input.
Can the text Super checkpoint inspect screenshots?
Do not assume so. If a required value appears only in an image, use a verified vision-language route or ask a person to inspect it.
Does installing the model connect it to Tabbit Browser?
No. Model serving, the agent client's local-tool permissions, and the Tabbit browser connection are separate setup steps.
Can I use Nemotron 3.5 Super in Pi?
Pi invokes the Tabbit skill as `/skill:tabbit`, but the research environment's offline model list did not contain this checkpoint. Verify model and provider availability on your own machine.
Should the agent approve a release after checking the page?
No. Have it prepare a checklist with visible source details, then let a human verify the account, environment, and approval policy before publishing.