To use Nex-N2-Pro on a page where you are already signed in, first confirm the exact open-weight revision and a local serving runtime that can emit tool calls. Then use an agent client that can run Tabbit CLI on the same machine as Tabbit Browser. Start with a read-only support-ticket check and review the named draft yourself. The model card documents Apache-2.0 weights and function calling, but it does not certify any specific agent/browser pairing. Official model card.
The useful distinction is between model access, tool calling, browser access, and site permission. A working checkpoint does not guarantee that the client understands its tool-call format. A browser session does not authorize edits to a ticket.
Key takeaways
Pin the model revision and read its license before downloading or serving it.
Check the serving runtime's tool-call parser. The Nex model card gives a specific SGLang parser option; verify the configuration for your chosen runtime.
Discover the Tabbit skill using the agent client's documented syntax, then test that the local Tabbit CLI launcher is reachable.
Use a separate task tab and read only the visible ticket fields you need.
Save a named draft and compare every value with the source page before taking action.
Preflight: confirm each layer
| Layer | What to verify | Stop if |
|---|---|---|
| Weights | nex-agi/Nex-N2-Pro, chosen revision, Apache-2.0 card | Revision or terms are unclear |
| Runtime | Hardware fit, serving endpoint, tool-call parser | Model serves text but does not produce usable tool calls |
| Agent client | Exact model route and local tool execution | Client silently substitutes another model or runs remotely |
| Tabbit | Skill discovery and local CLI launcher | The client cannot reach the local launcher |
| Website | Existing Tabbit Browser login and permitted ticket access | Page requests sign-in or user lacks access |
The model card gives vLLM and SGLang examples and says Nex-series function calling can be enabled with the qwen3_coder parser in SGLang. Treat that as a configuration lead, not a guarantee for every release. Confirm the selected revision and runtime documentation before starting the server. A hosted route such as early access through a provider is a separate option; check whether the provider still offers this exact model and whether your chosen client can use that route.
Skill discovery and launcher reachability are separate checks. Some clients use /skills; Pi uses /skill:tabbit. After loading the skill, verify the client process can invoke the installed Tabbit CLI. A remote runner needs a supported local handoff to reach a desktop browser. If it cannot reach the local launcher, stop and use a harmless export instead.
Read a support ticket without changing it
Use a test ticket or another record you are authorized to read. In Tabbit Browser, sign in normally. Ask the local agent to open only the supplied ticket URL and copy the visible ID, status, and link. Keep the scope narrow. Do not include account credentials, private customer text, or unrelated records in the prompt.
| Draft field | Evidence to keep | Reviewer check |
|---|---|---|
| Ticket ID | Visible ID and source URL | Does the ID match the page? |
| Status | Exact visible status label | Is it copied rather than inferred? |
| Link | Current ticket URL | Does it open the same authorized record? |
| Uncertainty | Missing or ambiguous field | Did the agent mark it unknown? |
| Boundary | “Read only” completion note | Did it avoid edits, replies, and navigation elsewhere? |
Use a named draft so you can find the result in Tabbit Browser. This is an illustrative prompt; it is not evidence that a Nex-N2-Pro integration was tested.
Read only the visible ticket fields at the supplied URL. Return the ticket ID, exact status label, and page URL. If a field is not visible, write “not visible.” Save the result as “Support ticket review — draft”. Do not edit, reply, submit, or open another record. Stop after saving the draft.Review each value against the page. If the status is unclear or the ID differs, correct the draft yourself and record the issue. Keep a separate task tab for this run so you can continue using your regular tabs. The first-task checklist gives a broader read-only setup.
Use Tabbit for the browser connection
Tabbit Browser keeps the website session you signed into. A compatible local agent can use Tabbit CLI to work in its own task tab, leaving your other tabs available. Follow the Tabbit CLI guide and existing-browser connection guide; choose MCP or CLI according to the client's local-access model. See Codex setup, what an agentic browser is, how browser agents work, and the Tabbit Browser overview.
This recommendation concerns the browser layer only. It does not claim Nex-AGI or a provider has a native Tabbit integration. Parent verified that the local CLI could reuse a signed-in session against a test fixture; that check did not involve Nex-N2-Pro or a real support system. Confirm your own model route, tool parser, account rights, and task boundaries before using the workflow.
FAQ
Is Nex-N2-Pro open source?
Its Hugging Face model card lists Apache-2.0 and provides weights. Check the current card and exact revision before downloading or deploying.
Does the model card prove browser-agent compatibility?
No. It documents model and serving details, but the agent client, tool-call parser, local bridge, and browser access need separate checks.
Can I reuse my signed-in browser session?
A local Tabbit CLI task can connect to the Tabbit Browser environment you signed into. Never pass credentials to the model.
How do I call the Tabbit skill?
Use the syntax your client documents. Some clients expose `/skills`; Pi uses `/skill:tabbit`. Confirm the local launcher works separately.
Can a remote agent connect to my browser?
Only if a supported local handoff exists. A remote model endpoint alone does not grant access to your desktop browser.
Should the first run update a ticket?
No. Read visible fields, save a named draft, and review it in Tabbit Browser before considering any write.